I always hated the fact that Mozilla implemented pocket into Firefox, since it isn't open-source. I always used Waterfox to solve that, which has pocket removed, but now that they acquired Pocket, I assume they will finally release the source code.
Jsyk the way Firefox is designed, dragging icons off of the ui into the customization panel for things like Pocket actually prevents the code that powers it from even running. Not true for all ui elements but I'm pretty sure it's true for any "system add-on" that they ship (or ever will ship... Dev tools come to mind as I believe they're breaking the dev tools out into a webextension)
I haven't had any issues with 64-bit firefox, but mileage may vary because it totally depends on which plugins/extensions you use. I've had more issues with them not being verified (signed), but my understanding is that's completely independent from 32 vs 64 bit builds, in that if the 32 bit ver is signed the 64 bit ver will be too and vice versa.
Does the 64 bit version behave/work properly with plugins and extensions yet?
Been using Waterfox (which is native 64-bit) for over a year now and never had any issues with plugins or extensions. Many plugins/extensions have been 64-bit long before win64 builds were release because Linux and Mac had 64-bit builds for a long time.
Also, Aurora as a branch is no more. The release model has been changed from Nightly- > Aurora -> Beta -> Release to Nightly -> Beta -> Release. Dev Edition users migrated to beta on desktop and aurora users on Android migrated to Nightly.
Also, Aurora as a branch is no more. The release model has been changed from Nightly- > Aurora -> Beta -> Release to Nightly -> Beta -> Release. Dev Edition users migrated to beta on desktop and aurora users on Android migrated to Nightly.
why not changed from nightly to aurora? shame on mozilla...
why not changed from nightly to aurora? shame on mozilla...
The DevEdition / Aurora was meant to be a stabilization channel with approximately 10x the users of Nightly. So the cycle was meant to be
Nightly - Experimental changes, rapid development
Aurora - Stabilization phase, focus is on fixing crashes in new features before beta
Beta - Polish phase - only ship-ready or nearly-ship-ready features here. Final stabilization for the release base
But the numbers goal didn't work out and it makes more sense to eliminate an unneeded stabilization phase and just hold features in nighty until they're ready to move to beta, so they can be iterated on more quickly. In the long run it will probably result in features reaching release about six to eight weeks earlier than they would have.
Firefox recently changed the way nightly builds are delivered. They now release a build every time a commit is done. This actually sped up progress a little because now they can pinpoint where exactly a bug happened, so they don't need the developer build anymore. They can combine them into one now. They will probably stick with the every month release cycle, but we will probably more features in every update now.
On a unrelated note, Firefox 53 now requires Rust compiler. 53 actually runs a lot faster for me then 52 did. I am guessing they are getting really close to officially being done transferring to Rust.
Firefox recently changed the way nightly builds are delivered. They now release a build every time a commit is done. This actually sped up progress a little because now they can pinpoint where exactly a bug happened, so they don't need the developer build anymore. They can combine them into one now. They will probably stick with the every month release cycle, but we will probably more features in every update now.
On a unrelated note, Firefox 53 now requires Rust compiler. 53 actually runs a lot faster for me then 52 did. I am guessing they are getting really close to officially being done transferring to Rust.
There will be no general access to preferences (about:config) planned.
There is no plan to allow WebExtensions to be able to change the default search engine.
There is no plan to change the appearance of tabs or interacting with the XUL in any way.
This bug suggests toolbars will be happening, but it hasn’t been assigned to anyone yet. There’s some discussion around if this is a good feature or not.
There is no plan to support XUL or theming or changes to the UI beyond some basic CSS changes similar to Chrome.
We aim to enable streaming of downloads in the downloads API.