MozillaZine

The first official 20191205 builds are out

Discussion about official Mozilla Firefox builds
Josa
 
Posts: 4806
Joined: July 28th, 2009, 4:52 pm

Post Posted December 4th, 2019, 8:15 am

Previous Nightly Builds thread 20191204

The first official 20191205 NIGHTLY builds are out
.The official Firefox 72 Beta 3 builds are not yet out

Previous NIGHTLY: 20191204 (Fx 73.0a1)
Previous BETA: 20191204 (Fx 72.0b2)

Mozilla Autoland Builds
Treeherder
Release Notes: NIGHTLY | BETA
Changelogs: NIGHTLY | BETA


Fixed:
    NIGHTLY +50
  1. #1597203
  2. #687441 [Core:CSS Parsing and Computation]-Subframes can cause a flash of unstyled content (FOUC) [mac]
  3. #770780 [Core:CSS Parsing and Computation]-Implement CSS3 text module text-underline-position [All]
  4. #1601025 [Core:CSS Parsing and Computation]-Optimize change-hint for text decoration changes that don't affect layout [Uns]
  5. #1598600 [Core:CSS Parsing and Computation]-Refactor InvalidationMap flags to use bitflags [Uns]
  6. #1600443 [Core:CSS Parsing and Computation]-Update cssparser. [Uns]
  7. #1202706 [Core:DOM: Core & HTML]-DOM APIs UseCounter should work on web workers [Uns]
  8. #1583614 [Core:DOM: Navigation]-Re-enable frameloader rebuilding on remoteness change by default again [Uns]
  9. #1596776 [Core:DOM: Navigation]-nsDocShellLoadState(DocShellLoadStateInit&) doesn't set mSHEntry [Uns]
  10. #1596701 [Core:DOM: Security]-Don't show wrong MIME type warning for failed HTTP load [Uns]
  11. #1534339 [Core:DOM: Security]-OriginAttributes.firstPartyDomain does not support IPv6 addresses [Uns]
  12. #1483631 [Core:DOM: Security]-Restrict nested permission requests (camera/microphone/geolocation/screensharing) with Feature Policy [Uns]
  13. #1601285 [Core:DOM: Selection]-Remove AutoPrepareFocusRange from Selection.cpp [Uns]
  14. #1591353 [Core:DOM: Service Workers]-Debug build does not start from profile manager (Assertion failure: !IsAcceptingPromises() immediately after selecting profile) [All]
  15. #1540921 [Core:DOM: Workers]-Intermittent /workers/WorkerGlobalScope-close.html | Test sending a message after closing. - [Uns]
  16. #1599327 [Core:Graphics: WebRender]-Use cluster scrollbar flags to select picture cache tile size. [Uns]
  17. #1595165 [Core:Graphics: WebRender]-WR tile splitting heuristics have oscillating behavior when invalidation areas are narrow [All]
  18. #1601376 [Core:Graphics: WebRender]-Windows webrender builds fail with rustc 1.39 in egl.rs [All]
  19. #1470591 [Core:IPC]-Add a fork server for launching content processes [Lin]
  20. #1600272 [Core:JavaScript Engine]-Crash [@ js::irregexp::RegExpCapture::min_match] with stack space exhaustion in worker [Lin]
  21. #1601074 [Core:JavaScript Engine]-Hit MOZ_CRASH(There should be room for registering the new object) at js/src/vm/TypeInference.cpp:3494 [Lin]
  22. #1561911 [Core:JavaScript Engine]-Unhandled rejected promise from `new ReadableStream(source)` if source.start() rejects [Uns]
  23. #1580053 [Core:Security: PSM]-Delegated Credentials Study Add-on [Uns]
  24. #1600433 [Core:Security]-Update pkcs11 crate. [Uns]
  25. #1596129 [Core:Storage: IndexedDB]-Make use of more abstract algorithms in IndexedDB code [Uns]
  26. #1601306 [Core:Web Painting]-Default themes are not applied correctly when they are switched from about:addons on Mac OS [mac]
  27. #1490571 [Core:Web Painting]-Not able to scroll after resizing responsive design mode view [Uns]
  28. #1592738 [Core:XPCOM]-update some rust crate dependencies [All]
  29. #1589930 [Core:XSLT]-Crash in [@ txFormatNumberFunctionCall::evaluate] [Win]
  30. #1596934 [DevTools:Application Panel]-Fix attaching to inactive service workers [Uns]
  31. #1579663 [DevTools:Console]-Allow data url background-image in styled console logs [Uns]
  32. #1567849 [DevTools:Console]-Allow the context menu to interact with targets [Uns]
  33. #1579090 [DevTools:Console]-WebConsole should handle ObjectFront when needed (for non-primitive Console API args + Evaluation results) [Uns]
  34. #1566891 [DevTools:Inspector: Changes]-Export Changes - Review telemetry probes for export options (due Firefox 73) [Uns]
  35. #1599635 [DevTools:Inspector]-Inspector markup view stays empty when refreshing jsfiddle [Uns]
  36. #1509804 [DevTools:Netmonitor]-Automatic export of HAR is broken due to EventEmitter refactor from last year [mac]
  37. #1595800 [DevTools:Responsive Design Mode]-Persist orientation state of device while in RDM [Uns]
  38. #1529917 [DevTools:Shared Components]-Remove VariablesViewController [Uns]
  39. #1591874 [DevTools:Storage Inspector]-Move VariablesView files to devtools/client/storage [Uns]
  40. #1601512 [Firefox Build System:General]-Point pkcs11 dependency to the upstream repo [Uns]
  41. #1600953 [Firefox:Address Bar]-The tip is permanently dismissed when clicking anywhere inside the tip but outside the "OK, Got It" button [All]
  42. #1600860 [Firefox:Address Bar]-[Interventions] The extension needs a way to install an update and restart for users who have opted out of automatic updates [Uns]
  43. #1600122 [Firefox:Enterprise Policies]-"ExtensionSettings" in policies.json does not allow users to disable addons [Uns]
  44. #1601014 [Firefox:General]-BrowserGlue._migrateUI should bail out early if no migration is necessary [Uns]
  45. #1584337 [Firefox:Normandy Client]-Clear enrollment IDs when Telemetry is disabled [Uns]
  46. #1596767 [Firefox:Page Info Window]-Image type row not updated correctly when moving through rows in page info window [Uns]
  47. #1431214 [Firefox:Session Restore]-Function _setCurrentURI seems to be unused [Uns]
  48. #1572140 [Toolkit:Add-ons Manager]-Remove compat overrides handling [Uns]
  49. #1455716 [Toolkit:General]-Simplify/rename nsIWebBrowserChrome::setStatus and setStatusWithContext [Uns]
  50. #1598717 [Toolkit:Password Manager]-Hide the "Firefox will save this password for this website" text when we wouldn't auto-save due to an existing login [All]

    Partial Landings/Diagnostic Patches:
  1. #1598053 [Core:JavaScript Engine]-Remove JS::EncodeInterpretedFunction [Uns]
  2. #1599465 [Core:JavaScript Engine]-Reduce allocations in BigInt functions and add fast-paths for uint64 BigInts [Uns]
  3. #1577825 [Core:JavaScript: GC]-SharedArrayBuffer memory is not accounted for [Uns]
  4. #1598164 [Core:Storage: IndexedDB]-Make transactions inactive during clone [Uns]
  5. #1600906 [Core:Storage: IndexedDB]-Reduce state in dom/indexedDB classes [Uns]

    Beta 2 -> Beta 3 Changelog +6
  1. #1592007 [Core:Security: PSM]-Upgrade Firefox 72 to use NSS 3.48 [All]
  2. #1591887 [Firefox Build System:General]-Upgrade Firefox 72 to use NSPR 4.24 [Uns]
  3. #1599258 [Firefox:Preferences]-Some dialog buttons lost their correct location [Uns]
  4. #1600281 [Firefox:Preferences]-Strange alignment of container buttons in preferences [Uns]
  5. #1599693 [Firefox:Search]-Search using <search engine set as default>" tooltip is not shown on search bar [All]
  6. #1599360 [Toolkit:Application Update]-Factor out appUpdater from aboutDialog-appUpdater.js into a jsm module [Uns]

Nightly 73 fixes since 20191202 (Gecko 72) ~168
Beta 72 fixes since 20191021 (Gecko 71) ~1761

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on December 5th, 2019, 10:46 am, edited 2 times in total.

Omega X

User avatar
 
Posts: 8185
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Post Posted December 4th, 2019, 1:04 pm

Ugh. The garbage bar is back.
Latest: Firefox/81.0 *ESR/78.3.0 - Mobile/81.1.1 - Thunderbird/78.2.2
Nightly: Nightly/83.0a1 - Mobile/GV 82.0a1 - Daily/83.0a1

Rabbit4
 
Posts: 949
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted December 4th, 2019, 1:53 pm

Omega X wrote:Ugh. The garbage bar is back.

just noticed , the " new an improved " cant see how its improved over the last one.

pgm_01
 
Posts: 10
Joined: September 16th, 2013, 7:30 am

Post Posted December 4th, 2019, 2:58 pm

Omega X wrote:Ugh. The garbage bar is back.

Anybody know how to make it stop? I don't see any megabar references in about:config.

Rabbit4
 
Posts: 949
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted December 4th, 2019, 3:07 pm

there should be a sticky made for people that wanna turn this off.
Last edited by Rabbit4 on December 4th, 2019, 5:00 pm, edited 1 time in total.

veryslow
 
Posts: 64
Joined: September 28th, 2013, 11:05 am

Post Posted December 4th, 2019, 4:34 pm

Mouse4 wrote:there should be a sticky made for people that wanna turn this off.

https://www.reddit.com/r/firefox/commen ... dress_bar/

https://www.reddit.com/r/FirefoxCSS/com ... ddressbar/

Uhm, this looks outdated, there's no browser.urlbar.megabar anymore? Adding browser.urlbar.megabar set to false doesn't help either.

Rabbit4
 
Posts: 949
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted December 4th, 2019, 4:42 pm

............
Last edited by Rabbit4 on December 4th, 2019, 5:00 pm, edited 1 time in total.

veryslow
 
Posts: 64
Joined: September 28th, 2013, 11:05 am

Post Posted December 4th, 2019, 4:45 pm

Okay, found the pref to disable the ugliness: browser.urlbar.update1 = false.

smsmith
Moderator

User avatar
 
Posts: 19878
Joined: December 7th, 2004, 8:51 pm
Location: Indiana

Post Posted December 4th, 2019, 6:01 pm

That's the spirit, chaps! Run a test browser, and turn off new features you don't like rather than help test them and file bugs or offer feedback in order to improve it!
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.

Rabbit4
 
Posts: 949
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted December 4th, 2019, 6:04 pm

smsmith wrote:That's the spirit, chaps! Run a test browser, and turn off new features you don't like rather than help test them and file bugs or offer feedback in order to improve it!

why test it when its that Ugly to begin with? obviously hardly many like the crap. + it gets disabled during Beta an or Release anyway so why not do it during Alpha .if Mozilla didnt bloat the browser up with useless features us users wouldnt have to disable them to begin with
Last edited by Rabbit4 on December 4th, 2019, 7:19 pm, edited 2 times in total.

Mupasa
 
Posts: 41
Joined: May 22nd, 2017, 12:53 pm

Post Posted December 4th, 2019, 6:56 pm

smsmith wrote:That's the spirit, chaps! Run a test browser, and turn off new features you don't like rather than help test them and file bugs or offer feedback in order to improve it!

Sorry, but this looks terrible and that's all :D And feedback in 1585912, 1588724.
Last edited by DanRaisch on December 5th, 2019, 5:11 am, edited 1 time in total.
Reason: Minor edit for language.

Are You A Wiiizard?
 
Posts: 400
Joined: August 30th, 2012, 4:27 am

Post Posted December 4th, 2019, 10:06 pm

smsmith wrote:That's the spirit, chaps! Run a test browser, and turn off new features you don't like rather than help test them and file bugs or offer feedback in order to improve it!


If it were anything non-UI related, sure. The problem is Firefox's UX team consistently ignore user's opinions and it's impossible to change their mind. There was plenty of feedback the first time around yet nothing has changed and they even used a different preference to enable it (what is up with "update1"? that's dreadful naming) so people who didn't want to see this garbage were forced to see it again.

DN123ABC
 
Posts: 545
Joined: January 9th, 2017, 10:10 am

Post Posted December 5th, 2019, 7:30 am

smsmith wrote:That's the spirit, chaps! Run a test browser, and turn off new features you don't like rather than help test them and file bugs or offer feedback in order to improve it!


What? Who asked for that? Most people want speed, compatibility, convenience, and reliability; and I would bet many or most are here looking for that, and willing to help with that.

Virtual_ManPL

User avatar
 
Posts: 2045
Joined: July 24th, 2008, 5:52 am

Post Posted December 5th, 2019, 7:37 am

Unfortunately, Mozilla and Mozilla developers (especially UI & UX) doesn't care at all in most cases about Firefox users opinions. =; Mozilla and Mozilla developers have their own agenda which they only blindly follow (sometimes copycaty Google-like). ](*,)
Virtualfox persona
Tired of constant Firefox UI changes? XUL extensions are not working anymore? Try SeaMonkey, Waterfox Classic, Pale Moon.

Gusar
 
Posts: 205
Joined: March 17th, 2006, 1:52 pm

Post Posted December 5th, 2019, 7:48 am

Are You A Wiiizard? wrote:they even used a different preference to enable it (what is up with "update1"? that's dreadful naming) so people who didn't want to see this garbage were forced to see it again.

It's update1 so it can be followed by update2, resulting in exactly what you wrote here - people who turned it off will be force-fed the next iteration.

@smsmith, Here's my feedback: This new thing adds nothing but distracting and annoying visual fluff. When the first iteration was foisted onto users, several of them thought it's a bug! The only improvement possible is to scrape the whole thing and stick to the current non-"mega"bar.

Now, if I wrote the above into a bugzilla comment, I seriously doubt the developers would respond to it in any way other than dismissal. So why bother. It's clear they'll go ahead with it, despite already having received more than enough negative feedback about it.

Return to Firefox Builds


Who is online

Users browsing this forum: No registered users and 3 guests