> WebRender will roll out to Windows 10 users with AMD graphics cards. This sounds awesome: https://mozillagfx.wordpress.com/2019/05/21/graphics-team-sh... > WebRender is a major rewrite of the Firefox rendering architecture using the same kind of GPU-based acceleration techniques used by games. I really hope it gets pushed to other Operating Systems as well in the future. Edit: Here's the link to their hacks mozilla…
Firefox 68.0
31–40 of 282 posts
Re: Firefox 68.0
#32Re: Firefox 68.0
#33I love Firefox. First thing I install on any new computer. Super happy they keep pushing the web forward. Not a fan of the chromium quasi monopoly (not that the folks behind it are bad, just that any monoculture is problematic). Thanks for pushing the web forward!
Re: Firefox 68.0
#34> Local files can no longer access other files in the same directory. What impact will this have on web development without a web server? It sounds like you won't be able to load CSS or JS.
So distributing documentation for offline use as a bunch of HTML + CSS files will now run into problems?
The release note refers to script access (XHR, DOM access across windows).
Re: Firefox 68.0
#35> WebRender will roll out to Windows 10 users with AMD graphics cards. This sounds awesome: https://mozillagfx.wordpress.com/2019/05/21/graphics-team-sh... > WebRender is a major rewrite of the Firefox rendering architecture using the same kind of GPU-based acceleration techniques used by games. I really hope it gets pushed to other Operating Systems as well in the future. Edit: Here's the link to their hacks mozilla…
It's a shame it hasn't made it over to Mac yet - graphics card options are a lot more limited there so you'd figure it would be easier to support. But I suppose it's a much smaller market share.
Re: Firefox 68.0
#36> Local files can no longer access other files in the same directory. What impact will this have on web development without a web server? It sounds like you won't be able to load CSS or JS.
i wrote some offline webapps for my mom with html, css and js. she just opens a local html file on her android tablet. will they stop working?
That said, if they work in Chrome right now they will also work in Firefox 68.
Re: Firefox 68.0
#37> Local files can no longer access other files in the same directory. What impact will this have on web development without a web server? It sounds like you won't be able to load CSS or JS.
For what it's worth, I'm still able to open and use Doxygen HTML docs without running a web server. Looks like it loads both CSS and JS. So I'm not sure what the changenote actually means.
Script running in a page loaded from file:// will not be able to access the DOM or text of any other file:// URLs, other than the one it's running in.
Re: Firefox 68.0
#381) Regarding WebRender: Maybe I'm a bit out of the loop, but aren't they working on Servo? It seems, WebRender is a Gecko thing. I'm confused. 2) I'm also confused about the state of Gecko Embedding. As far as I know many are jumping to Chromium instead of Gecko. What's the plan there? Is Chromium better/easier to embed? Will I be able to embed Servo at some point?
Re: Firefox 68.0
#39"Cryptomining and fingerprinting protections are added to strict content blocking settings in Privacy & Security preferences." my first reaction is it's really sad to see this. looks like something Google blackmailed them into adding. maybe Im missing some aspect to this.. but why is mining crypto bad but showing ads is not? I rather mine coins/ether/whatever for the website owners than see more ads moving away from…
Crypto-mining scripts are mostly silent; if your computer doesn’t have a loud fan to spin up, you’re hardly able to even tell one is running other than on its eventual impact on battery life. As such, they’re a favoured tool of script-kiddies who deface websites. They take over a site, and then drop a crypto-miner onto the site to make themselves money, otherwise leaving everything intact. Sometimes even the site own…
This is being used by anybody who can sneak a javaascipt into your page or an iFrame that you embed, which has become too easy to do. When it comes down to it, IMO, site owners are responsible for what ads and scripts they allow to be served via their page, but I think I'm in the minority on that opinion.
Ad networks (the more reputable ones anyway) are playing a cat and mouse game of allowing a Turing complete js environment and trying to prevent its use for doing particular pieces of math. I'm glad Firefox is joining in as well, but I'd be happier if we didn't have this problem to begin with.