Discussion about official Mozilla Firefox builds
Josa
Posts: 7360 Joined: July 28th, 2009, 4:52 pm
Post
by Josa » October 29th, 2017, 5:41 am
Previous Nightly Builds thread
20171028
The first official 20171029 NIGHTLY builds are out
. The Official Firefox 57 Beta 13 builds are not yet out
Previous NIGHTLY:
20171028 (Fx 58.0a1)
Previous BETA:
20171027 (Fx 57.0b12)
Mozilla Inbound Builds
Treeherder
Release Notes:
NIGHTLY |
BETA
Changelogs:
NIGHTLY |
BETA
Fixed :
NIGHTLY +9
#1412547 [Core:Audio/Video]-avoid unused lambda captures in MediaDecoder.cpp [All][]
#1412251 [Core:CSS Parsing and Computation]-stylo: style sharing doesn't work with XBL / Shadow DOM. [Uns][]
#1409928 [Core:Disability Access APIs]-[e10s a11y] Use handler cache for accessibles retrieved from IAccessibleHypertext [Win][]
#1401609 [Core:Graphics: WebRender]-Some canvases on perf-html.io don't update [All][[wr-mvp] [gfx-noted]]
#1412546 [Core:JavaScript Engine]-avoid -Wunused-private-field warnings in WasmTypes.h [All][]
#1407114 [Core:Layout: Text]-Tamil fonts (in bold) have issues on Firefox Linux [Lin][[webcompat] ]
#1229384 [Core:Memory Allocator]-Out of memory crash in moz_abort | pages_commit [Win][[gfx-noted]]
#1406856 [Core:Security: PSM]-Re-plumb nsISSLStatus.idl to carry with it the whole nsIX509CertList [Uns][[psm-backlog]]
#1412430 [Firefox:Theme]-Move light theme tabstrip vibrancy rule to MacOS-specific stylesheet [Mac][[reserve-photon-visual]]
Partial Landings/Diagnostic Patches :
None
Beta 12 -> Beta 13 Changelog +3
#1409444 [Core:CSS Parsing and Computation]-stylo: Crash in rand::weak_rng [Win][]
#1397441 [Core:Security: PSM]-Make sure HPKP preload expiration date is accurate for 57 [All][[psm-blocked] ]
#1409101 [Firefox:Developer Tools: Debugger]-Editor is occasionally empty [Uns][]
Nightly 58 fixes since 20170921 (Gecko 57)
~1991
Beta 57 fixes since 20170802 (Gecko 56)
~3528
Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by
Josa on October 29th, 2017, 8:33 am, edited 1 time in total.
Xetmes
Posts: 676 Joined: December 7th, 2011, 8:54 am
Location: Poland/Germany
Post
by Xetmes » October 29th, 2017, 6:25 am
I was able to hide search box from newtab page, but I can't change value browser.newtabpage.rows;3 to 4. Seams to be hardcoded?
1for-matik
Posts: 118 Joined: August 9th, 2006, 5:05 am
Location: France
Contact:
Post
by 1for-matik » October 29th, 2017, 6:37 am
So, my bug (
1412586 ) seems to be hardware acceleration related.
A second computer (with nVidia GT 610) seems not to be affected, but my first (AMD R7 240 with updated drivers) is still affected when hardware acceleration is activated.
Lurtz
Posts: 359 Joined: June 12th, 2016, 12:25 pm
Post
by Lurtz » October 29th, 2017, 6:45 am
1for-matik wrote: So, my bug (
1412586 ) seems to be hardware acceleration related.
A second computer (with nVidia GT 610) seems not to be affected, but my first (AMD R7 240 with updated drivers) is still affected when hardware acceleration is activated.
Are you using WebRender? Otherwise I don't see how that regression range can be responsible.
What happens if you only disable video hardware acceleration?
1for-matik
Posts: 118 Joined: August 9th, 2006, 5:05 am
Location: France
Contact:
Post
by 1for-matik » October 29th, 2017, 7:13 am
Well, forget about it... seems the bug resolved itself after disabling/re-enabling hardware acceleration.
Lurtz
Posts: 359 Joined: June 12th, 2016, 12:25 pm
Post
by Lurtz » October 29th, 2017, 8:12 am
Josa
Posts: 7360 Joined: July 28th, 2009, 4:52 pm
Post
by Josa » October 29th, 2017, 8:34 am