Problems with WURFL.JS coding

For those who like to stay on the client
jonny
Posts: 2
Joined: Mon Mar 14, 2016 2:27 pm

Problems with WURFL.JS coding

Postby jonny » Mon Mar 14, 2016 2:29 pm

Hello,

When trying to add your javascript file to a website that is running Content Security Policy (CSP) Level 2. We get the following error:

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src........."

Poorly coded Javascript still uses eval as its a security risk. Any chance to update your JS script. Or are we allowed to recode it ourselves...?

I am sure the world would love to use a safer script as well. :idea:

aaronp
Posts: 244
Joined: Wed Dec 09, 2015 12:39 pm

Re: Problems with WURFL.JS coding

Postby aaronp » Mon Mar 14, 2016 4:06 pm

Hi John,

Thank you for letting us know. I have notified my engineering team regarding this case and will follow up with you when I receive an update.

In the meantime, please feel free to let me know if you have any other questions or concerns.

Thanks,

Aaron

jonny
Posts: 2
Joined: Mon Mar 14, 2016 2:27 pm

Re: Problems with WURFL.JS coding

Postby jonny » Mon Mar 14, 2016 4:27 pm

Please post update here, as we love using WURFL.js but the code definitely needs updating.

Fensut
Posts: 1
Joined: Mon Jul 14, 2025 9:12 am

Re: Problems with WURFL.JS coding

Postby Fensut » Mon Jul 14, 2025 9:13 am

I ran into some strange issues while implementing WURFL.JS devices weren’t being identified correctly, and the layout kept breaking. During a coding forum chat, someone brought up the vibe coding meaning to explain how staying in sync with a tool’s logic flow helps solve problems faster. That mindset really helped me troubleshoot effectively.


Who is online

Users browsing this forum: No registered users and 1 guest