Firefox is the first major browser to support CSS Grids out of the box.<p><a href="https://developers.google.com/web/updates/2017/01/css-grid" rel="nofollow">https://developers.google.com/web/updates/2017/01/css-grid</a> is a simple introduction to it.<p><a href="http://gridbyexample.com/" rel="nofollow">http://gridbyexample.com/</a> is probably the best reference site.<p><a href="https://tympanus.net/codrops/css_reference/grid/" rel="nofollow">https://tympanus.net/codrops/css_reference/grid/</a> is another very nice single-page reference.<p>Some technical examples from Igalia, who have been implementing Grid in Blink and Webkit: <a href="http://igalia.github.io/css-grid-layout/" rel="nofollow">http://igalia.github.io/css-grid-layout/</a><p>Some lovely creative examples from Mozilla's Jen Simmons:<p><a href="http://labs.jensimmons.com/" rel="nofollow">http://labs.jensimmons.com/</a><p><a href="http://labs.jensimmons.com/2016/" rel="nofollow">http://labs.jensimmons.com/2016/</a>
Firefox is one of those projects that just keeps on giving, and it's all thanks to the hard work put in by all the contributors. It's easy to forget that sometimes. We use Firefox headlessly to render videos at <a href="https://www.musicvideodispenser.com" rel="nofollow">https://www.musicvideodispenser.com</a> , a task that certainly wasn't the initial intended use-case for that browser, but it still works, and we have the Firefox team to thank for that!
I did a lot of work on Firefox's NPAPI implementation over the past decade. Improving that code was rewarding in that it had very tangible benefits for Firefox users but it was pretty clear that improving Firefox's code was only going to get us so far, and not far enough. The system is a mess and I couldn't be happier to see Firefox dropping support. I hope I can be the one to rip out the code altogether some day.
What I like most about firefox is the mobile version supports addons like ublock origin. In mobile Chrome the support for add blockers is not really well supported.
> Added support for WebAssembly, an emerging standard that brings near-native performance to Web-based games, apps, and software libraries without the use of plugins.<p>I've been watching this from the sidelines... what's the best way to dive into WebAssembly? Or is it just waiting for tooling to catchup to produce it for WebAssembly-enabled browsers to execute?
> Enhanced Sync to allow users to send and open tabs from one device to another.<p>If you haven't used this, try it out, it's a fantastic feature.
I use it all the time to send a page I'm reading on my phone to my laptop, and vice versa.
Starting from this release, Firefox now requires PulseAudio for sound on Linux [1]. ALSA can still be enabled at build time for now, but is not supported.<p>[1] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1247056" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1247056</a>
I just added Firefox 52 to Browserling. You can try this new version at this URL without installing it:<p><a href="https://www.browserling.com/firefox/52/news.ycombinator.com" rel="nofollow">https://www.browserling.com/firefox/52/news.ycombinator.com</a><p>If the demand is too high then you'll have to wait in a queue for a while to try it. I'm adding more servers right now to let more people try it without waiting.
Congrats Firefox team! I've been using the latest Nightly releases (for container tabs!) as my daily driver and it has been a rock-solid experience.<p>Thanks for the hard work
> Removed support for Netscape Plugin API (NPAPI) plugins other than Flash. Silverlight, Java, Acrobat and the like are no longer supported.<p>Good bye, you will be missed (not).
And still no support for <input type="date"> . I just can't believe Firefox is behind Edge on this one. I'm using Firefox as main browser for years now, and it feels so bad when I always need to use a polyfill when developing a form with date field - to support Firefox. It's embrassing that Chrome supported it since... Chrome 20, in 2012.
You might want to switch yourself to the ESR branch if you depend on add-ons that will not update to the new Web Extensions API. The old extensions model is scheduled to be removed in FF 57, later this year. But 52 ESR will be supported until at least mid-2018.<p>Edit: switched "plugins" to "add-ons".
Past few days I've been making a Befunge JIT that targets WASM: <a href="https://github.com/serprex/Befunge/blob/master/funge.js" rel="nofollow">https://github.com/serprex/Befunge/blob/master/funge.js</a><p>Ended up finding that Firefox 52 is overly accepting in validation. Dead code is allowed to pop from an empty stack, whereas in Chrome that's not allowed (as per spec). It's fixed already in next versions of Fx
<i>sigh</i> I had to switch to Chromium because they've broken + disabled HW acceleration on Linux, and my 2016 netbook is too slow to browse amazon or read news without it. Here is the bug:<p><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=594876" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=594876</a><p>In the release notes for 52, it says hangouts is broken. I wonder if this means all of webrtc is broken or not.<p>Regressing "stable" features like these is creating serious problems for end users. I wish they'd focus on keeping the ship afloat instead of continuing to chase the new shiny. I really don't like relying on google (or any other ad/surveillance shop) for my web browser.
Firefox for Android recently stopped showing me the "Send to Firefox" option in the share menu. I previously used it all the time to send tabs to my desktop. Does anyone know what happened or how to get it back?
Doesn't mention if the major problem I have with Firefox 51 is fixed. It makes a new, unauthenticated request every time I do View Source rather than showing the source of the page I'm looking at, which is an extreme PITA.<p>If View Source works properly, that'd be worth upgrading for immediately.
If you're using Tree Style Tab and this upgrade causes new tabs to appear after a delay of many seconds... setting browser.tabs.animate to false resolved it for me (macOS 10.12).
Mozilla says 'Enabled multi-process Firefox for Windows users with touch screens', however on my Dell XPS 13 it still says multiprocess windows are 'Disabled by accessibility tools' in about:support, which was the touch screen issue. Any ideas?
Despite of my media.gmp-provider.enabled setting being set to false Firefox makes a connection to ciscobinary.openh264.org on port 80 and downloads the h264 decoder binary provided by Cisco.<p>Does this mean that the library is being downloaded (and executed) using plain HTTP without any authentication? Sounds like a nice target for QUANTUM style MITM attacks.
I'm still rockin Firefox 33 (released 2014) on one of my PCs. Sad to observe websites which fail and throw errors without any grace including big sites like Netflix and others.<p>Strange errors and broken functionality usually without any mention of my browser being the problem. That's sloppy development. A browser from 2014 isn't "Netscape 3".<p>Signed up to Google Firebase recently. Tried navigating to the console on my PC with Firefox 33, "there was an error completing your request". That's because I was using a browser from 2014. No mention of that in the error. At first I thought the service was down, then I tried a newer browser.<p>Backwards compatibility or at least graceful degradation and error handling is accessibility. Your site either has it or it doesn't.
> Removed support for Netscape Plugin API (NPAPI) plugins other than Flash. Silverlight, Java, Acrobat and the like are no longer supported.<p>That's really, really bad. At this point Firefox was the only browser which was supporting Java on Linux. I am forced to stick to the 51 version (52 64bit ESR does not support Java also).<p>You may ask, why on earth do you need Java inside your browser in 2017? My company, which does not support Linux, uses Java applet to create system-wide VPN connections to the client's networks and Firefox was the only choice.
It's frustrating that multi-process is <i>still</i> not enabled on my touchscreen windows laptop. The about:support page says "Disabled by accessibility tools". Feel like I've been waiting for this feature to arrive for years.
Here's a more hacker oriented write-up at <a href="https://hacks.mozilla.org/2017/03/firefox-52-introducing-web-assembly-css-grid-and-the-grid-inspector/" rel="nofollow">https://hacks.mozilla.org/2017/03/firefox-52-introducing-web...</a> (published today). Discussion (if it comes) at <a href="https://news.ycombinator.com/item?id=13812145" rel="nofollow">https://news.ycombinator.com/item?id=13812145</a>
How is Firefox Android working for everyone? I can't seem to get video player working on some website like bloomberg.com, otherwise I'm a fan of it.
What happened to TLS 1.3 which was supposed to land in Firefox 52? (At least according to <a href="https://threatpost.com/mozilla-turning-tls-1-3-on-by-default-with-firefox-52/121461/" rel="nofollow">https://threatpost.com/mozilla-turning-tls-1-3-on-by-default...</a>)<p>Not that I'm ungrateful; Firefox is my preferred browser.
I have one question: when I hit "." in twitter.com will the whole thing hang whilst it crunches through the updates?<p>I moved from chrome to firefox and so far this is my one complaint. This and I believe the CPU usage is higher for the same number of tabs open.
Why does Mozilla make it hard to run the sync server (easily) on our own? Just give a docker file. Instead you need a sync server, your own account server.. such poor technical design. These are small features that will make many stick to Firefox.
Did they bump the minimum Android version required?<p>I do not see the release via the Play store app, but the web site shows it.<p>For a project that seems to bill itself as being for the people, they seems awful quick at dropping backwards compatibility.
What are the supported operating systems, I don't see any list of supported OS's ? i did the upgrade and it just crashed on startup (on windows 7 enterprise edition), Installing from scratch didn't help either.
Still no hardware accelerated video on Linux. Everytime Mozilla adds new features, I am reminded of this:<p><a href="https://xkcd.com/619/" rel="nofollow">https://xkcd.com/619/</a>
What percent of Google Voice users will abandon Firefox now that v52 breaks a key component of their workflow?<p><a href="https://gsuiteupdates.googleblog.com/2017/02/google-hangouts-temporary-issues-with-firefox.html" rel="nofollow">https://gsuiteupdates.googleblog.com/2017/02/google-hangouts...</a><p>Ironically, Mozilla has stated that breaking all these user plugins is part of some strategy to <i>regain</i> market share and "influence web standards". Now that it's actually happening, I'm hoping more people will see how it's not going to work.