The first official 20171120 builds are out

[Josa]

Previous Nightly Builds thread 20171119

The first official 20171120 NIGHTLY builds are out
.The Official Firefox 58 Beta 5 builds are not yet out

Previous NIGHTLY: 20171119 (Fx 59.0a1)
Previous BETA: 20171116 (Fx 58.0b4)

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


Fixed:

1. NIGHTLY +13
2. #1416450
3. #1415090 [Core:Audio/Video: Playback]-Move "reopen on error" off the main thread [Uns][]
4. #1417794 [Core:Audio/Video: Playback]-Move Adts.h, AnnexB.h and H264.h to dom/media/platform/agnostic/bytestreams [Uns][]
5. #1418059 [Core:CSS Parsing and Computation]-Crash in core::option::expect_failed | geckoservo::glue::Servo_StyleSet_GetBaseComputedValuesForElement [All][]
6. #1418872 [Core:CSS Parsing and Computation]-move ControlCharVisibilityDefault() out of nsCSSParser [Uns][]
7. #1418220 [Core:DOM: Animation]-Drop AnimationUtils::IsCoreAPIEnabled(ForCaller) and use nsContentUtils::AnimationsAPICoreEnabled instead [All][]
8. #1418836 [Core:Gecko Profiler]-No restyle markers inside refresh ticks anymore [All][]
9. #1418106 [Core:JavaScript Engine]-Assertion failure: !PromiseHasAnyFlag(*promise, 0x40), at js/src/builtin/Promise.cpp:3376 [Lin][[jsbugmon:update]]
10. #1415843 [Core:Layout]-Remove some dubious frame construction code. [Uns][]
11. #1417376 [Core:Layout]-Convert nsPoint parameters to passing by const reference instead values [Uns][]
12. #1418156 [Core:Preferences: Backend]-Make PrefHashEntry smarter [Uns][]
13. #1370040 [Core:Widget: Cocoa]-Don't need to use the private API -[NSWindow _cornerMask] [Mac][tpi:+]
14. #1416980 [Core:XML]-Remove nsIExtendedExpatSink [All][]

1. Partial Landings/Diagnostic Patches:
   None

1. Beta 4 -> Beta 5 Changelog +16
2. #1414490
3. #1416450
4. #1416473 [Core:Audio/Video: Playback]-Youtube throws and error after moving to a new position/time for the second time [Uns][]
5. #1416614 [Core:Graphics: WebRender]-Crash in mozilla::layers::HostIPCAllocator::SendPendingAsyncMessages [All][[wr-mvp]]
6. #1416618 [Core:Internationalization]-Cannot show short date format (yy/MM/dd'('ddd')') correctly [Win][]
7. #1415549 [Core:JavaScript Engine]-Assertion failure: JS::StringIsASCII(args_), at js/src/jscntxt.cpp:698 [Lin][[ossfuzz] [jsbugmon:update]]
8. #1415013 [Core:Layout]-Assertion failure: !parent->HasAnyOfFlags(Element::kAllServoDescendantBits), at /src/layout/style/ServoStyleSet.cpp:995 [Uns][]
9. #1417959 [Core:Security: Process Sandboxing]-Remove alternate desktop from Level 4 [Win][sb+]
10. #1415300 [Firefox:Developer Tools: Debugger]-Update Debugger Frontend (11-7) [Uns][]
11. #1416358 [Firefox:Developer Tools: Debugger]-Update Debugger Frontend (11-10) [Uns][]
12. #1408738 [Firefox:Theme]-[macOS] [Photon] The Window Control Buttons could be placed some pixels to the right to match the Mock [Mac][[reserve-photon-visual]]
13. #1414721 [Firefox:Tours]-Colors of Onboarding nav icons are inconsistent [All][[photon-onboarding][photon-onboarding-newui]]
14. #1415836 [Toolkit:Form Autofill]-[Form Autofill] The text in autocomplete footer wraps incorrectly [Uns][[form autofill:MVP]]
15. #1417032 [Toolkit:Form Autofill]-[Form Autofill] Credit card number is missing after choosing "update" or "create new" in the doorhanger [All][[form autofill:MVP]]
16. #1417316 [Toolkit:Form Autofill]-[Form Autofill] Can not preview or fill in data when triggering suggestion dropdown twice [All][[form autofill:MVP]]
17. #1415596 [Toolkit:Video/Audio Controls]-Grey haze over video while buffering [All][]

Nightly 59 fixes since 20171113 (Gecko 58) ~348
Beta 58 fixes since 20170921 (Gecko 57) ~2705

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide

[Are You A Wiiizard?]

Getting really fast and choppy scrolling on: https://ghost-recon.ubisoft.com/wildlan ... terference
Other pages seem fine, is it possible it's the webpage doing it? In Edge it scrolls fast still but not as fast and still seems smooth.

[TheVisitor]

Getting really fast and choppy scrolling on: https://ghost-recon.ubisoft.com/wildlan ... terference
Other pages seem fine, is it possible it's the webpage doing it? In Edge it scrolls fast still but not as fast and still seems smooth.

Site is fast and sorta choppy in IE11, Chrome and latest Nightly here... I would guess its likely the page.

[Peja Stija]

Still youtube 720p60 problems. Streams in FF nightly are choppy, dropping massive amounts of frames.
Same stream played in same resolution, in Vivaldi : Fluent as can be.

Stream (only available for next 4 hours) https://www.youtube.com/watch?v=64pChNUemwQ

I only encounter those problems in FF nightly for 60fps streams btw, normal (50fps ?) streams play fine.

[TheVisitor]

Still youtube 720p60 problems. Streams in FF nightly are choppy, dropping massive amounts of frames.
Same stream played in same resolution, in Vivaldi : Fluent as can be.

Stream (only available for next 4 hours) https://www.youtube.com/watch?v=64pChNUemwQ

Those problems don't happen in FF nightly for non-60fps streams btw.

Seems to play ok here - watching 'stats for Nerds'.. only 2 dropped frames in 5000 frames... I only have a 10meg DSL line to boot... so running good actually.,

[Peja Stija]

Still youtube 720p60 problems. Streams in FF nightly are choppy, dropping massive amounts of frames.
Same stream played in same resolution, in Vivaldi : Fluent as can be.

Stream (only available for next 4 hours) https://www.youtube.com/watch?v=64pChNUemwQ

Those problems don't happen in FF nightly for non-60fps streams btw.

Seems to play ok here - watching 'stats for Nerds'.. only 2 dropped frames in 5000 frames... I only have a 10meg DSL line to boot... so running good actually.,

Thanks for testing, i personally don't think this is bandwidth related since the same stream plays fluent in any other browser I tested, but most probably rendering related.

[Omega X]

I'm not seeing any frame drops on YouTube.

[koboltzz]

Can someone reproduce the following bug?

-clean profile, start firefox
-create new tab containers (give them a name you like) by deleting the defaut ones ('shopping' and so on)
-close firefox, add user_pref("browser.startup.page", 3); to prefs.js (load all tabs on startups)
-start firefox again
-result/bug: All of your tab containers with custom names are deleted, default ones ('shopping') are restored

[toolong]

Can someone reproduce the following bug?

-clean profile, start firefox
-create new tab containers (give them a name you like) by deleting the defaut ones ('shopping' and so on)
-close firefox, add user_pref("browser.startup.page", 3); to prefs.js (load all tabs on startups)
-start firefox again
-result/bug: All of your tab containers with custom names are deleted, default ones ('shopping') are restored

I am confused. Just why would you do any of this?

[bjherbison]

I followed the steps given and also tried a variation and I can't reproduce the container custom name reset issue.

A couple of months ago I noticed a container custom name reset issue--that was caused by testing with the then Nightly and the then release with the same profile.

[koboltzz]

I am confused. Just why would you do any of this?

Then you don't understand to use session restore with container tabs.

@bjherbison
thank you for testing This 'container custom name reset issue' (good name) I noticed since the last two weeks but yesterday I found out which setting is the cause...

[WaltS48]

I am confused. Just why would you do any of this?

Then you don't understand to use session restore with container tabs.

Well, I didn't understand that

-close firefox, add user_pref("browser.startup.page", 3); to prefs.js (load all tabs on startups)

would restore the session.

I would just bookmark the sites in the containers, in a bookmark folder and use "Open All in Tabs", or "Restore Previous Session".

I also thought prefs.js is what I see when I open about:config, and that user.js should be used to modify that, but I leave all that stuff alone. No need for me to reinvent the wheel.

[smsmith]

This is the part that confuses me.

-close firefox, add user_pref("browser.startup.page", 3); to prefs.js (load all tabs on startups)
-start firefox again

Why would you ever do it that way? You were mucking about in the options to begin with to setup your containers, why not set Firefox to restore previous session right there? Why go through this step that has the potential to ruin your prefs file? Also, no "regular user" will do it that way, so bug impact is fairly low. I try not to question why a person does things in a certain way, because to each his own, but this one just seems overly silly to me.

[Josa]

This thread is closed, please use the next one.