Jump to content
CCleaner Community Forums
nodles

The Firefox/Mozilla Thread

Recommended Posts

Quantum Flow Engineering Newsletters:

 

#3

#4

#5

#6

 

These weeks in firefox....

 

#13

#14

#15 (I'm mentioned in this one!)

 

Release notes for nightly.... https://blog.nightly.mozilla.org/2017/04/24/release-notes-for-nightly/

 

Though I'll be honest, I used to make the MozillaZine nightly threads and they're much more comprehensive if you're interested in nitty-gritty. A user by the name of Josa now maintains these threads here: http://forums.mozillazine.org/viewtopic.php?f=23&t=3029746&sid=50ac71e408503d819c4a7cbcf2da5d10

 

 

 

Out of process web extensions now available for testing:

https://wiki.mozilla.org/WebExtensions/Testing-out-of-process

 

Fathom: a framework for understanding web pages:

https://hacks.mozilla.org/2017/04/fathom-a-framework-for-understanding-web-pages/

 

AMO on android has a new look:

https://blog.mozilla.org/addons/2017/04/11/amo-new-look-android/

 

 

 

 

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.

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

https://blog.mozilla.org/blog/2017/04/19/first-big-bytes-project-quantum/

 

53 is only the beginning :) Firefox 57 is the target for another few big chunks of quantum.

Share this post


Link to post
Share on other sites

WebExtensions/RoadMapFirefox57https://wiki.mozilla.org/WebExtensions/RoadMapFirefox57

 

 


Some highlights:

- The work on Chrome compatibility is mostly complete.
- Before Firefox 57 lands, we will complete out of process extensions
- There is no plan to support other APIs like history, bookmarks etc [in Android] by Firefox 57.
- Per above, providing arbitrary filesystem access in WebExtensions is not currently planned.
- 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.

via reddit

 

 

 

Quantum up close:

https://hacks.mozilla.org/2017/05/quantum-up-close-what-is-a-browser-engine/

 

Thunderbird's future home:

https://blog.mozilla.org/thunderbird/2017/05/thunderbirds-future-home/

 

TWIS 101:

https://blog.servo.org/2017/05/08/twis-101/

Share this post


Link to post
Share on other sites

Wait what is "chrome compatibility" why are they dumbing down customization of themes and,toolbars

Share this post


Link to post
Share on other sites

Wait what is "chrome compatibility" why are they dumbing down customization of themes and,toolbars

 

The WebExtensions API is meant to replace the current addon model, but they don't plan to turn it on by default until it has reached feature parity with Chrome's API in order to make it easier for chrome extension developers to port their extensions to firefox

 

I believe they're moving the front end UI code from XUL to html/css (part of Quantum DOM?) and in doing so removing a lot of customization. I think userchrome.css will still be functional, I think more advanced themes that rely on XUL functions will not be.

Share this post


Link to post
Share on other sites

 

The WebExtensions API is meant to replace the current addon model, but they don't plan to turn it on by default until it has reached feature parity with Chrome's API in order to make it easier for chrome extension developers to port their extensions to firefox

 

I believe they're moving the front end UI code from XUL to html/css (part of Quantum DOM?) and in doing so removing a lot of customization. I think userchrome.css will still be functional, I think more advanced themes that rely on XUL functions will not be.

The end of Classic Theme Restorer. Dreading it <_<

 

 

Share this post


Link to post
Share on other sites

 

The end of Classic Theme Restorer. Dreading it <_<

 

 

52 ESR should still work for another year :)

Share this post


Link to post
Share on other sites

52 ESR should still work for another year :)

 

With a possible chance of an extension when they add up the results this summer.

Share this post


Link to post
Share on other sites

 

52 ESR should still work for another year :)

If it's going it's going, no point delaying it lol. I'll either have to live with the default layout, or finally make the move to Vivaldi that I've been threatening since forever :lol:

Share this post


Link to post
Share on other sites

If it's going it's going, no point delaying it lol. I'll either have to live with the default layout, or finally make the move to Vivaldi that I've been threatening since forever :lol:

 

Guess again. Vivaldi already dropped XP/Vista support. The only other browser that I know of that works on XP/Vista (and also 2000 if it's any consolation) is Midori. It is still in early development and I don't know if they have any plans to drop support for those old systems, but the current versions runs on them. Well, Waterfox also managed to get XP/Vista working, while keeping updates with Firefox releases, but only 64-bit versions and some features have been disabled.

Share this post


Link to post
Share on other sites

 

Guess again. Vivaldi already dropped XP/Vista support

Don't use either so not a problem (though only a matter of time before developers start dropping support for Win7 - THEN I'll be pissed off)

Share this post


Link to post
Share on other sites

Firefox 54 may see 4 content processes on by default (up from 1):

 

https://bugzilla.mozilla.org/show_bug.cgi?id=1367244

 

the number of content processes can be modified by the user in about:config with dom.ipc.processcount or through a panel in the preferences (I've seen mockups but this module hasn't yet landed in Nightly)

 

PEN 2:

https://dolske.wordpress.com/2017/05/23/photon-engineering-newsletter-2/

 

 Preview Form Autofill in Nightly:

https://blog.nightly.mozilla.org/2017/05/23/preview-form-autofill-in-firefox-nightly/

Share this post


Link to post
Share on other sites

I have my process count on my PC set to 8, but I think I may increase it more. The autofill looks nice and will come in handy for people who do a lot of online shipping or whatever, especially since lots of people don't like saving information on a website.

 

I think soon I will go back to using Firefox beta and would even be willing to enable telemetry data for them to help development.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...