The first official 20181104 builds are out

[Josa]

Previous Nightly Builds thread 20181103

The first official 20181104 NIGHTLY builds are out
.The Official Firefox 64 Beta 7 builds are not yet out

Previous NIGHTLY: 20181103 (Fx 65.0a1)
Previous BETA: 20181102 (Fx 64.0b6)

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


Fixed:

1. NIGHTLY +4
2. #1426492 [Core:DOM]-Add an assertion to limit XBL bindings in the content process [Uns][[xbl-in-content]]
3. #1503473 [Core:Editor]-Handle Enter key press on TextEditor as insertLineBreak rather than insertParagraph [All][]
4. #1504237 [Core:ImageLib]-Some animation WebPs with lossy-compression aren't rendered correctly [Uns][]
5. #1501502 [Core:JavaScript Engine]-Assertion failure: IsObjectValueInCompartment(v, compartment()), at js/src/vm/NativeObject.h:1040 with ReadableStream [Lin][[jsbugmon:update,bisect]]

1. Partial Landings/Diagnostic Patches:
   None

1. Beta 6 -> Beta 7 Changelog +4
2. #1500543 [Core:Document Navigation]-Extremely spammy warning |WARNING: NS_ENSURE_TRUE(browserChrome) failed: file [snip]/docshell/base/nsDocShell.cpp, line 12726| [Uns][]
3. #1405814 [Core:Graphics: WebRender]-Crash in mozilla::layers::ScrollMetadata::ScrollMetadata [All][[wr-reserve]]
4. #1493743 [Core:Layout: Text and Fonts]-Crash in gfxFontGroup::BuildFontList [Mac][]
5. #1501680 [Firefox:Security]-Cookies sent while SSL report submission on incoming.telemetry.mozilla.org [Uns][]

Nightly 65 fixes since 20181022 (Gecko 64) ~587
Beta 64 fixes since 20180904 (Gecko 63) ~2159

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide

[ashleylai87]

Just asking while playing with DOH.....

What exactly "network.notify.IPv6" setting do?

EDIT:
Anyway, I noticed if I set firefox to use DOH (cloudflare), firefox tends to connect using ipv4 first.

I had set :
network.trr.early-AAAA to true
network.http.fast-fallback-to-IPv4 to false

and of course, network.notify.IPv6 to true.

Is this a bug or what?
However, after I run firefox for like 20 minutes or so, firefox will connect via ipv6 just fine.
Once i close firefox and re-execute firefox, firefox will connect via ipv4 again.

[johnp_]

From what I can tell it's basically whether or not to ask the OS to notify FF on a network interface change (i.e. IPv6 address assignment / connectivity change) and was disabled in bug 1245059 for windows due to at least Windows 10 having issues with its Teredo Tunneling Adapter frequently vanishing and triggering bogus notifications and thereby causing connection timeouts in FF. More information here.

Regarding your edit I would also expect IPv6 preference under those conditions.

[ashleylai87]

From what I can tell it's basically whether or not to ask the OS to notify FF on a network interface change (i.e. IPv6 address assignment / connectivity change) and was disabled in bug 1245059 for windows due to at least Windows 10 having issues with its Teredo Tunneling Adapter frequently vanishing and triggering bogus notifications and thereby causing connection timeouts in FF. More information here.

Regarding your edit I would also expect IPv6 preference under those conditions.

If I don't use DOH, firefox will prefer ipv6 connection right away.
Oh well, I don't exit firefox that often.........

[Josa]

This thread is closed, please use the next one.