The first official 20180813 builds are out

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

The first official 20180813 builds are out

Post by Josa »

Previous Nightly Builds thread 20180812

The first official 20180813 NIGHTLY builds are out
.The Official Firefox 62 Beta 17 builds are not yet out

Previous NIGHTLY: 20180812 (Fx 63.0a1)
Previous BETA: 20180810 (Fx 62.0b16)

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

  1. NIGHTLY +15
  2. #1481905 [Core:CSS Parsing and Computation]-Text in dropdown under "App Functions" is not visible (was: Page not Loading after 59 version) [Uns][]
  3. #1482677 [Core:CSS Parsing and Computation]-remove unused BorrowedAtom [Uns][]
  4. #1482694 [Core:CSS Parsing and Computation]-Crash in style::traversal::compute_style [All][]
  5. #1480060 [Core:Disability Access APIs]-aria-multiselectable should be supported on role tablist [All][]
  6. #1464251 [Core:Editor]-crash near null in [@ mozilla::HTMLEditor::SplitStyleAbovePoint] [Uns][]
  7. #1482012 [Core:Editor]-Split HTMLEditor::Paste() for internal use [All][]
  8. #1482013 [Core:Editor]-Split HTMLEditor::SetInlineProperty() for internal use [All][]
  9. #1482015 [Core:Editor]-Split HTMLEditor::RemoveInlineProperty() for internal use [All][]
  10. #1478178 [Core:Layout: Text]-Assertion failure: applyState.mGaps.mHandled == applyState.mGaps.mCount (Unprocessed justification gaps), at src/layout/generic/nsLineLayout.cpp:3191 [Uns][]
  11. #1481998 [Core:MFBT]-Make mozilla::Hash{Map,Set}'s entry storage allocation lazy [Uns][[overhead:45k]]
  12. #1479501 [Core:Security: PSM]-set fallback-limit pref to TLS 1.3 by default for Firefox 62 [Uns][]
  13. #1477598 [DevTools:about:debugging]-Show/update/debug extensions [Uns][]
  14. #1476580 [DevTools:Font Inspector]-Italic toggle is looking very pixelated on a non-retina screen [Uns][]
  15. #1477310 [Firefox:Security]-Enable the new certificate error pages by default in Nightly [Uns][]
  16. #1482637 [Firefox:Site Identity and Permission Panels]-Missing trailing period in string for lack of blockable content (contentBlocking.notDetected) [Uns][]
  1. Partial Landings/Diagnostic Patches:
  2. #1481097 [Core:General]-Remove workarounds for gcc 4.x bugs [Uns][]
  1. Beta 16 -> Beta 17 Changelog +11
  2. #1480517
  3. #1475010 [Core:Canvas: WebGL]-SharedSurfaceANGLE not getting a KeyedMutex [Win][gfx-noted]
  4. #1471466 [Core:Disability Access APIs]-When opening a new tab from menus, focus incorrectly lands on document in previous tab [Win][]
  5. #1451172 [Core:DOM]-Assertion failure: JS_IsExceptionPending(cx), at /builds/worker/workspace/build/src/obj-firefox/dom/bindings/EventListenerBinding.cpp:26 [Uns][[stockwell needswork:owner]]
  6. #1475073 [Core:DOM: Security]-Pass individual CORS errors as categories to web console error messages [Uns][[domsecurity-active]]
  7. #1481833 [DevTools:Console]-SVG animVal breaks console [Uns][]
  8. #1475589 [Firefox:Address Bar]-formatValue in URL bar doesn't get re-run when dragging tab to new window [Uns][[fxsearch]]
  9. #1472435 [Firefox:Sync]-bookmarks failed: Error: Error(s) encountered during statement execution: UNIQUE constraint failed [Uns][]
  10. #1464938 [Toolkit:Add-ons Manager]-Crash in AsyncShutdownTimeout | profile-change-teardown | Extension shutdown: * [All][]
  11. #1470965 [WebExtensions:General]-WebExtensionPolicy.cpp raises "Assertion failure: int32_t(mRefCnt) > 0 (dup release)" after accessing addonPolicy property on a principal object instance [Uns][]
  12. #1477015 [WebExtensions:Storage]-Select the storage.local backend during the extension startup [Uns][]

Nightly 63 fixes since 20180626 (Gecko 62) ~2020
Beta 62 fixes since 20180507 (Gecko 61) ~1987

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on August 14th, 2018, 7:19 am, edited 1 time in total.
User avatar
Posts: 327
Joined: May 13th, 2017, 11:36 am
Location: Oregon, United States, Earth

Re: The first official 20180813 builds are not yet out

Post by Mark12547 »

Nightly just broke my credit union web site ( when I try to log on with warning, "Warning: Potential Security Risk Ahead" with the code, "MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED". Clicking on "Continue" displays "MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED" with an option to add an exception, which I did to view my current account and bill payer activity. Apparently the credit union's vendor for online banking is using a certificate issued by Symantec Corporation.

However, when in the online banking of my credit union and I drill down into the Credit Card section, I get the error, "Warning: Potential Security Risk Ahead" with this paragraph, " has a security policy called HTTP Strict Transport Security (HSTS), which means that Nightly can only connect to it securely. You can’t add an exception to visit this site." Since I cannot add an exception to, I have to use something else at this time to view my credit card transactions or to schedule to pay my credit card bill.

Nightly just broke When one calls up an individual auction, instead of seeing the description, one sees "Warning: Potential Security Risk Ahead" and clicking on "Continue" reveals the reason" " uses an invalid security certificate. The certificate does not come from a trusted source. Error code: MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED". There is no option to add an exception.

Nightly just broke the MyChart web site where my doctor is located when I go to and click on "My Chart". Same song. I was able to add an exception.

All three sites work fine in Chrome Version 68.0.3440.106 (Official Build) (64-bit).

The Firefox Nightly I am using is 63.0a1 (2018-08-13) (64-bit) Build-id 20180813220525 under Windows 10 (64-bit).

It looks like Firefox Nightly is finally invalidating all certificates issued by Symantec, but it comes a bit of a shock even when one knows what is going on. E. g., Firefox to distrust all TLS certificates issued by Symantec, and, from the Mozilla Security Blog, Update on the Distrust of Symantec TLS Certificates.

Or, if you don't want to be an early adopter of this particular feature, in about:config set security.pki.distrust_ca_policy to 1.
Posts: 940
Joined: February 21st, 2011, 10:14 am

Re: The first official 20180813 builds are not yet out

Post by Fanolian »

Mark12547 wrote:Nightly just broke my credit union web site .....
Google and Mozilla were coordinating with this matter and aligning their policies as close as possible.
I don't use a pre-release version of Chrome, but according to Google's blog, Chrome canary is also blocking all certs from Symantec.

Both stable versions are planned to release within 1 week (Chrome: Oct 16; Firefox: Oct 23).
Posts: 1039
Joined: October 6th, 2003, 5:40 am
Location: Bolton, MA, US

Re: The first official 20180813 builds are not yet out

Post by bjherbison »

I just updated to the latest Nightly and viewed an eBay auction with no warning. I also tried with a new profile, no warnings there either.

Could you give an URL for an auction that you get the warning for?
Posts: 6983
Joined: July 28th, 2009, 4:52 pm

Re: The first official 20180813 builds are out

Post by Josa »