The first official 20180822 builds are out

[Josa]

Previous Nightly Builds thread 20180821

The first official 20180822 NIGHTLY builds are out
.The Official Firefox 62 Beta 20 builds are not yet out

Previous NIGHTLY: 20180821 (Fx 63.0a1)
Previous BETA: 20180821 (Fx 62.0b19)

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


Fixed:

1. NIGHTLY +74
2. #1478849
3. #1484559
4. #1484753
5. #1480036 [Core:Audio/Video: MediaStreamGraph]-Allow scaling all MSG volume with a pref [Uns][]
6. #1417050 [Core:Audio/Video: Playback]-Add support for AV1 in mp4 [Uns][]
7. #1484242 [Core:Audio/Video: Playback]-Limit the number of simultaneously active decoders when using MediaCapabilities [Uns][]
8. #1429298 [Core:CSS Parsing and Computation]-Implement path() function for offset-path [Uns][]
9. #1484690 [Core:CSS Parsing and Computation]-Panic when having two stylesheet <link>s with the same href in ShadowRoot. [Uns][]
10. #1485252 [Core:CSS Parsing and Computation]-add MallocSizeOf impls for 128-bit integers [Uns][]
11. #1364392 [Core:DOM: Security]-Have openLinkIn() provide the correct triggeringPrincipal [Uns][[domsecurity-active]]
12. #1484773 [Core:DOM]-Crash in mozilla::dom::DocumentOrShadowRoot::RemoveSheet [Mac][]
13. #1484944 [Core:Document Navigation]-Remove nsSHEnumerator [All][]
14. #1484602 [Core:Editor]-Don't reuse variables in WillDeleteSelection. [Uns][]
15. #1484110 [Core:Editor]-Split HTMLEditor::CheckSelectionStateForAnonymousButtons() for internal use [All][]
16. #1484113 [Core:Editor]-Split HTMLEditor::GetFirstRow() for internal use [All][]
17. #1484115 [Core:Editor]-Split HTMLEditor::GetNextRow() for internal use [All][]
18. #1483245 [Core:Graphics: Layers]-Add telemetry probe measuring total paint thread rasterization time [Uns][[gfx-noted]]
19. #1483772 [Core:Graphics: Layers]-Crash in mozilla::layers::ClientPaintedLayer::RenderLayerWithReadback [Win][]
20. #1483566 [Core:Graphics: Text]-Update Graphite to version 1.3.12 [All][[third-party-lib-audit][gfx-noted]]
21. #1479196 [Core:Graphics: WebRender]-Browser crashes with a html file full of emojis, if you drag-and-drop the file from desktop to browser [Uns][]
22. #1452513 [Core:Graphics: WebRender]-blob-invalidation: Crash in mozalloc_abort | abort | libxul.so@0x3d1f718 | libxul.so@0x3d1f708 | libxul.so@0x3d0f260 | webrender::resource_cache::ResourceCache::update_resources [All][]
23. #1440648 [Core:JavaScript Engine: JIT]-Need to handle JSTRY_FOR_OF in JSScript::hasLoops()? [Uns][]
24. #1483182 [Core:JavaScript Engine]-Assertion failure: !cx->isExceptionPending(), at js/src/vm/JSContext-inl.h:331 with OOM [Lin][[jsbugmon:]]
25. #1473957 [Core:JavaScript Engine]-Assertion failure: cx->compartment() != untaggedReferent->compartment(), at js/src/vm/Debugger.cpp:5271 [Lin][[jsbugmon:update]]
26. #1479430 [Core:JavaScript Engine]-Assertion failure: cx->realm() == group->realm(), at js/src/vm/TypeInference.cpp:3853 [Lin][[jsbugmon:update]]
27. #1483188 [Core:JavaScript Engine]-Assertion failure: resultCapability.resolve(), at js/src/builtin/Promise.cpp:3016 [Lin][[jsbugmon:update]]
28. #1484382 [Core:JavaScript Engine]-Use mozilla::ScopedExit instead of custom types when reasonable (js/src) [Uns][]
29. #1473228 [Core:JavaScript: Internationalization API]-Add Intl.RelativeTimeFormat.prototype[@@toStringTag] [Uns][]
30. #1484420 [Core:JavaScript: Internationalization API]-Move locale-related functions into js/public/LocaleSensitive.h that isn't #include'd in jsapi.h [All][]
31. #1484587 [Core:Layout: Block and Inline]-Put the new behavior of overflow-wrap: break-word behind a pref [Uns][]
32. #1485023 [Core:Layout: Scrolling and Overflow]-Replace conditionals on PresShells when suppressing displayports to asserts inside gfxScrollFrame [Uns][]
33. #1483311 [Core:Networking: DNS]-provide a "disable TRR" loadflag for devtools [Uns][[necko-triaged][trr]]
34. #1484984 [Core:Networking]-Avoid writing past the logical length of a string in networking code [Uns][]
35. #1469117 [Core:Networking]-Socket timeout is left engaged when set to infinity and later back [Uns][[necko-triaged][tb]]
36. #1484868 [Core:Permission Manager]-Add the nsIPermissionManager::removeByType() API [Uns][]
37. #1485114 [Core:Permission Manager]-Avoid creating nsPermission objects in the permission manager needlessly [All][]
38. #1484809 [Core:Preferences: Backend]-Put class nsRelativeFilePref into its own include file [Uns][]
39. #1479071 [Core:Printing: Setup]-Changes to the paper size made in Page Setup do not persist, not reflected in print dialog [Mac][]
40. #1480275 [Core:SVG]-Assertion failure: IsInComposedDoc(), at src/dom/svg/SVGUseElement.cpp:234 [Uns][]
41. #1483248 [Core:Web Replay]-Allow recording child processes to handle TabChild deletion [Uns][]
42. #1483365 [Core:Web Replay]-Crash in mozilla::recordreplay::RR_mach_msg [Mac][]
43. #1483240 [Core:Web Replay]-Disable plugins when recording/replaying [Uns][]
44. #1481350 [Core:Web Replay]-Don't try to handle messages sent to child-allocated browsers [Uns][]
45. #1483242 [Core:Web Replay]-Ensure recording filenames are unique [Uns][]
46. #1483256 [Core:Web Replay]-Record atomic accesses in MemoryTextureReadLock [Uns][]
47. #1484848 [Core:Widget]-Remove the XPCOM component registrations for window and child window [All][]
48. #1484846 [Core:XPCOM]-Export the city hash of the install path [Uns][]
49. #1484844 [Core:XPCOM]-Make nsINIParser mutable [Uns][]
50. #1471743 [Core:XPCOM]-remove STRICT_FAKE_SYMLINKS code from nsLocalFileWin [All][]
51. #1479758 [DevTools:Console]-<kbd>?</kbd>+<kbd>?</kbd> does not navigate the console input history when cursor at the beginning of the input [Uns][[boogaloo-mvp]]
52. #1482798 [DevTools:Console]-Moving cursor in CodeMirror JsTerm when output is tall causes slow Reflow [Uns][]
53. #1483166 [DevTools:Console]-Refactor evalWithDebugger in the webconsole actor [Uns][]
54. #1485125 [DevTools:Inspector]-Lazy load the Device Modal in RDM [Uns][]
55. #1484811 [DevTools:Inspector]-Left align the toolbar controls when RDM is left aligned [Uns][]
56. #1481443 [DevTools:Shared Components]-Alt-b and Alt-f move back or forward one word and add a unicode character at the same time in DevTools console [Mac][]
57. #1482498 [Firefox:Bookmarks & History]-Replace mozMatchesSelector usage with matches in browser-places.js [Uns][]
58. #1483148 [Firefox:Bookmarks & History]-javascript: bookmarklets no longer work after disallowInheritPrincipal bug 1466801 [Uns][[fxsearch]]
59. #1484415 [Firefox:General]-Blacklist PrivateBrowsingUtils.jsm for use at content process startup [Uns][[overhead: 5k]]
60. #1485014 [Firefox:PDF Viewer]-Update pdf.js to version 2.0.775 [All][]
61. #1478112 [Firefox:Tabbed Browser]-Sort out how to best call `this._getSwitcher().requestTab` and `this.updateCurrentBrowser` during tabpanels selectedIndex change [Uns][]
62. #1483935 [Firefox:Tabbed Browser]-Tab count on "warn on close multiple tabs" when quitting the browser is wrong [Uns][[mozfr-community]]
63. #1484422 [Firefox:Theme]-Clean up fullscreen window controls styling [All][]
64. #1478477 [Firefox:Theme]-Developer Edition Mac installer has no background image [Mac][]
65. #1484512 [Firefox:Theme]-Split up places.css and only load relevant parts of it [Uns][[ntim-intern-project]]
66. #1471657 [Firefox:Theme]-Update Firefox Nightly DMG Background to HiDPI [Mac][]
67. #1443561 [Firefox:Theme]-WebExtension themes additional backgrounds alignment should be relative to the toolbox [Uns][[blocking-static-themes-fx][ntim-intern-project]]
68. #1485099 [Firefox:Tracking Protection]-Add some logging to the AntiTracking component for the saving and reading of storage access permissions [All][]
69. #1482220 [Firefox:WebPayments UI]-Figure out why add/edit form strings don't appear on Nightly builds [All][[webpayments]]
70. #1440282 [Toolkit:Crash Reporting]-Breakpad DWARF symbol dumper doesn't handle DW_AT_ranges [Uns][]
71. #1355346 [Toolkit:Downloads API]-CocoaFileUtils::AddOriginMetadataToFile() called at the end of file downloads can do sync IPC on the main thread [Uns][[qf:p1:f64][fxperf:p1]]
72. #1485133 [Toolkit:Video/Audio Controls]-Remove Web Animation polyfill in video controls [Uns][]
73. #1484796 [Web Compatibility Tools:Go Faster]-Add console logging to site patches via Content Scripts [Uns][]
74. #1475842 [WebExtensions:General]-browser.search.search: make name parameter optional [Uns][]
75. #1418602 [WebExtensions:Themes]-Allow theming sidebars [Uns][[ntim-intern-project] [blocking-static-themes-fx]]

1. Partial Landings/Diagnostic Patches:
2. #1437065 [Core:JavaScript Engine: JIT]-wasm: Specialize monomorphic calls from JS to wasm [Uns][]
3. #1470914 [Core:Security: PSM]-Upgrade Firefox 63 to use NSS 3.39 [Uns][[psm-assigned]]

1. Beta 19 -> Beta 20 Changelog +6
2. #1484051
3. #1443830 [Core:Gecko Profiler]-Back out the last patch from bug 785440 from Beta due to installer size regressions [Uns][]
4. #1484380 [Core:Security: Process Sandboxing]-[Mac] Default the Mac Flash sandbox to level 1 [Mac][]
5. #1483134 [DevTools:Inspector]-Inspector/3-pane scroll bar expands over headers on zoom or devTools height resize [All][]
6. #1469943 [Firefox:Enterprise Policies]-Policy: set a custom app update URL [All][]
7. #1481447 [Firefox:Search]-Switch browser.search.log to a lazy preference getter. [Uns][]

Nightly 63 fixes since 20180626 (Gecko 62) ~2444
Beta 62 fixes since 20180507 (Gecko 61) ~2040

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide

[RaiseMachine]

Is anybody else using Dev Ed. 62b17 64bit on Win10 and not had the b18 or b19 updates yet?

[Mark12547]

Is anybody else using Dev Ed. 62b17 64bit on Win10 and not had the b18 or b19 updates yet?

I have them installed and use them for testing at times, and I try to keep them updated (Help -> About Firefox).

Beta just updated to 62.0b19 (64-bit).

Developer is still at 62.0b17 (64-bit).

This is on Windows 10 (64-bit).

https://www.mozilla.org/en-US/firefox/developer/all/ claims it wants to download the installer for 62.0b19 when looking at Windows 64-bit en-US.

First guess is that the updater for Developer 62.0b17 is broken.

I don't have time to pursue this now; maybe tomorrow morning.

[RaiseMachine]

Never mind Mark; Developer now updated to 62.0b19.

[Tomatoshadow2]

Are there any differences between Beta and Developer Edition, now that they are on the same channel?

[Mark12547]

Never mind Mark; Developer now updated to 62.0b19.

Ah, I just fired up my PC and, yes, Dev had updated.

Are there any differences between Beta and Developer Edition, now that they are on the same channel?

Actually, Dev is on the aurora channel.

Beta is on the beta channel.

While they are presently at the same version of Firefox, there are some settings and some other changes that is suppose to make Dev more friendly to developers including, if I am not too mistaken, recognizing an about:config setting that allows loading of unsigned extensions so developers would be able to, well, develop extensions.

During most of the between-releases time, Beta and Dev are kept at the same version.

But it gets complicated from about a week before the versions roll through about a week or two after the versions roll.

Typically, about two weeks or so before the versions roll, the feature set of Nightly is set and code changes are typically mostly limited to bug fixes. Then about 5 days or so before the versions roll, Nightly (63.0a1) is forked and the forked code cleaned up (the code that will not "ride the rails" is excluded), and this code arrives in Dev (as 63.0b_) a few days before the roll.

Meanwhile, about 5 to 7 days before the versions roll, Beta (as 62.0b__) is modified to become a Release candidate (as 62.0). As issues are found and code is cleaned up, there will be additional Release candidates (also labeled 62.0).

During this time, Release (61.___) is still Release (61.___).

When the developers are satisfied that the Release Candidate (62.0) in the Beta channel is good, this code is saved and will roll into the Release Channel (as 62.0) on the day of the release. The internal updater for a small percent of Firefox Release users (on 61.___) will update Firefox to the new Release (to 62.0). If no spike in problems, the developers will let the internal updater of more Firefox Release users update those installs. Unless a major problem is discovered, usually Help -> About Firefox will update to the latest for that channel.

Typically the day of the roll date, Beta (was 61.0b__) will receive Dev (62.0b__) minus the code changes and parameters that make Dev especially friendly for developers. Then the Beta and Dev channels are typically kept at the same point release until about a week before the next version roll.

On or shortly after the roll date for Nightly, Nightly (63.0a1) will be renumbered to the next Nightly (64.0a1). Usually very little is done that night other than change the version number. Then for the next six weeks or so Nightly receives a bunch of code changes, including new features, experimental code (some of which may never make it to Release, such as studies), work on long-term projects (like WebRender), telemetry changes to capture metrics on suspected elusive bugs or suspected inefficiencies. And then that typically brings us back to within a couple weeks of the next versions roll.

If none of this makes sense, it may be due to sleep deprivation since this heat wave has made it difficult for me to sleep, and the smoke from the Pacific Northwest fires is giving me a bit of a headache.

[ashleylai87]

Anyone encounter address bar focus problem after opening new tab via extension such as foxygesture recently?
I was planning to write at foxygesture developer git until I saw someone had written before me.

https://github.com/marklieberman/foxyge ... issues/269

Since this address bar focus issue happened last week (not sure when), I suspect it is firefox related issue.
I am hoping someone could open a bug for this at bugzilla?

[Tomatoshadow2]

Never mind Mark; Developer now updated to 62.0b19.

Ah, I just fired up my PC and, yes, Dev had updated.

Are there any differences between Beta and Developer Edition, now that they are on the same channel?

Actually, Dev is on the aurora channel.

Beta is on the beta channel.

While they are presently at the same version of Firefox, there are some settings and some other changes that is suppose to make Dev more friendly to developers including, if I am not too mistaken, recognizing an about:config setting that allows loading of unsigned extensions so developers would be able to, well, develop extensions.

During most of the between-releases time, Beta and Dev are kept at the same version.

But it gets complicated from about a week before the versions roll through about a week or two after the versions roll.

Typically, about two weeks or so before the versions roll, the feature set of Nightly is set and code changes are typically mostly limited to bug fixes. Then about 5 days or so before the versions roll, Nightly (63.0a1) is forked and the forked code cleaned up (the code that will not "ride the rails" is excluded), and this code arrives in Dev (as 63.0b_) a few days before the roll.

Meanwhile, about 5 to 7 days before the versions roll, Beta (as 62.0b__) is modified to become a Release candidate (as 62.0). As issues are found and code is cleaned up, there will be additional Release candidates (also labeled 62.0).

During this time, Release (61.___) is still Release (61.___).

When the developers are satisfied that the Release Candidate (62.0) in the Beta channel is good, this code is saved and will roll into the Release Channel (as 62.0) on the day of the release. The internal updater for a small percent of Firefox Release users (on 61.___) will update Firefox to the new Release (to 62.0). If no spike in problems, the developers will let the internal updater of more Firefox Release users update those installs. Unless a major problem is discovered, usually Help -> About Firefox will update to the latest for that channel.

Typically the day of the roll date, Beta (was 61.0b__) will receive Dev (62.0b__) minus the code changes and parameters that make Dev especially friendly for developers. Then the Beta and Dev channels are typically kept at the same point release until about a week before the next version roll.

On or shortly after the roll date for Nightly, Nightly (63.0a1) will be renumbered to the next Nightly (64.0a1). Usually very little is done that night other than change the version number. Then for the next six weeks or so Nightly receives a bunch of code changes, including new features, experimental code (some of which may never make it to Release, such as studies), work on long-term projects (like WebRender), telemetry changes to capture metrics on suspected elusive bugs or suspected inefficiencies. And then that typically brings us back to within a couple weeks of the next versions roll.

If none of this makes sense, it may be due to sleep deprivation since this heat wave has made it difficult for me to sleep, and the smoke from the Pacific Northwest fires is giving me a bit of a headache.

Yes makes perfect sense, thanks Mark, appreciate it.

[Tomatoshadow2]

Anyone encounter address bar focus problem after opening new tab via extension such as foxygesture recently?
I was planning to write at foxygesture developer git until I saw someone had written before me.

https://github.com/marklieberman/foxyge ... issues/269

Since this address bar focus issue happened last week (not sure when), I suspect it is firefox related issue.
I am hoping someone could open a bug for this at bugzilla?

Do you have steps to reproduce this?

[ashleylai87]

Anyone encounter address bar focus problem after opening new tab via extension such as foxygesture recently?
I was planning to write at foxygesture developer git until I saw someone had written before me.

https://github.com/marklieberman/foxyge ... issues/269

Since this address bar focus issue happened last week (not sure when), I suspect it is firefox related issue.
I am hoping someone could open a bug for this at bugzilla?

Do you have steps to reproduce this?

Sure, here a 49 seconds small video https://ufile.io/9xvro

EDIT: The initial two tabs was opened via keyboard CTRL + T. The last two tabs was opened via foxygesture.

[smsmith]

Anyone encounter address bar focus problem after opening new tab via extension such as foxygesture recently?
I was planning to write at foxygesture developer git until I saw someone had written before me.

https://github.com/marklieberman/foxyge ... issues/269

Since this address bar focus issue happened last week (not sure when), I suspect it is firefox related issue.
I am hoping someone could open a bug for this at bugzilla?

Do you have steps to reproduce this?

Sure, here a 49 seconds small video https://ufile.io/9xvro

EDIT: The initial two tabs was opened via keyboard CTRL + T. The last two tabs was opened via foxygesture.

No issue here opening a new tab with Foxy Gestures and having address bar focus.

Foxy Gestures 1.21. Nightly 63.0a1 from 8/22 (20180822100104)

[Josa]

This thread is closed, please use the next one.