When the HSTS preload script was reworked to use async/await in bug 1436369,
`fetchstatus` would create an asynchronous xml http request and then attempt to
access a response header from it. However, there was nothing to ensure that the
request had completed before this code ran. This patch ensures that the request
has completed before the response header is used.
This patch also replaces a lingering instance of `Ci.nsISSLStatusProvider` that
should have been changed to `Ci.nsITransportSecurityInfo` in bug 1475647.
Finally, this patch removes the old, redundant getHSTSPreloadList.js in
security/manager/tools as well as the unused nsSTSPreloadList.errors file in
security/manager/ssl.
Differential Revision: https://phabricator.services.mozilla.com/D2807
--HG--
extra : moz-landing-system : lando
Prior to bug 1453751 responsive design mode relied on the parent process seeing
that no favicon had been loaded and so defaulting to the root favicon for a
site. This would have meant that on some occasions responsive design mode didn't
show the correct favicon for pages that specified their own. This change passes
all the link related messages to the parent so favicons, feeds and searches
should work correctly.
Differential Revision: https://phabricator.services.mozilla.com/D3032
--HG--
extra : moz-landing-system : lando
This patch implements the Symantec distrust plan on Nightly only for now.
Differential Revision: https://phabricator.services.mozilla.com/D2959
--HG--
extra : moz-landing-system : lando
Basically it tests in which order various tab events are dispatched, so the old name
didn't make sense, and it will be more suited for a new test specific to onHighlighted.
MozReview-Commit-ID: Kj8GZfHA0Ap
--HG--
rename : browser/components/extensions/test/browser/browser_ext_tabs_onHighlighted.js => browser/components/extensions/test/browser/browser_ext_tabs_events_order.js
extra : rebase_source : 243155e897d08bd70091c6a7ee11b4671a098ef2
And require it for taskcluster build already, because it doesn't harm and lets
me put all the yml changes in the same commit.
I gave up cross-compiling for OSX after a few tries and after realizing it
wasn't enough with cctools and such, but that I also needed the Mac SDK, for
which I don't have permission...
Differential Revision: https://phabricator.services.mozilla.com/D2664
--HG--
extra : moz-landing-system : lando
They'll be reopened, so there's no security benefit, but this causes Activity
Monitor to not report the processes as 'not responding'.
Differential Revision: https://phabricator.services.mozilla.com/D2855
--HG--
extra : moz-landing-system : lando
Set the "network.trr.disable-ECS" pref to false to disable.
MozReview-Commit-ID: GE6L8Vpvuu0
Differential Revision: https://phabricator.services.mozilla.com/D2933
--HG--
extra : moz-landing-system : lando
The default character set that is used to read sub-scripts using
`mozJSSubScriptLoader` is ASCII. Scripts for Activity Stream contains strings
which are encoded in UTF-8, and therefore, reading them in ASCII will display
the strings incorrectly.
Differential Revision: https://phabricator.services.mozilla.com/D3160
--HG--
extra : moz-landing-system : lando
In the genuine adb binary, when it received 'host:kill' command, it exits the
server process soon [1]. Whereas, in our mock adb.py which is based on
SocketServer.TCPServer in python, when we call
SocketServer.TCPServer.shutdown() in the case of 'kill-server' command, the
server process doesn't exit soon since the shutdown() function just sets a
flag [2] and serve_forever() polls it [3] every |poll_interval| seconds,
|poll_interval| is 0.5 seconds by default. Thus it's possible that new incoming
requests are processed during polling.
This is the real cause of the race condition that the adb server still keeps
alive when 'adb kill-server' finished. So we don't need to the workaround
for the race condition.
[1] 4039051d6d/adb/adb.cpp (1049)
[2] 65b5ef02ec/Lib/socketserver.py (L248)
[3] https://docs.python.org/2/library/socketserver.html#SocketServer.BaseServer.serve_forever
Differential Revision: https://phabricator.services.mozilla.com/D3169
This icon is copied from the common globe icon, except that it supports
context-fill.
Differential Revision: https://phabricator.services.mozilla.com/D3097
--HG--
extra : rebase_source : fb33161d0dead6a42566cdd3c95df8216a607811
This patch introduces a new preference:
devtools.aboutdebugging.network-locations
- this preference is a string pref, that should be a stringified
JavaScript array.
- the default value is "[]".
- the module supports getting, adding, removing and observing
network locations.
Differential Revision: https://phabricator.services.mozilla.com/D3096
--HG--
extra : rebase_source : c167a689bccda547f12b4970775c2e7feab49553
In order to reuse the button and ellipsis styles in the Connect page,
I would like to move the corresponding styles to a common stylesheet.
Differential Revision: https://phabricator.services.mozilla.com/D3095
--HG--
extra : rebase_source : 4a2eef73edf9b648776dbb3c6ba094160f4e99e8
Avoid processing anon content in nsCanvasFrame, then getting more anon content
via AccessibleCaretEventHub::Init. Instead call Init before creating the custom
content container. We could also throw a script runner at it I guess, but this
prevents the reentrancy issue.
Avoid cloning nodes during layout, just use the same node (already cloned in
InsertAnonymousContent) instead.
The RemoveChild in GetAnonymousContent to handle the reframes instead of cloning
around is a bit hacky, but I don't think it's really worth extending
PostDestroyData for this special case.
Differential Revision: https://phabricator.services.mozilla.com/D1889
David Keeler
irrationalagent
Michael Kaply
Ciure Andrei
Nan Jiang
Henri Sivonen
Ting-Yu Lin
Mark Hammond
Chris Manchester
Francois Marier
Dave Townsend
Oriol Brufau
Emilio Cobos Álvarez
Alex Gaynor
Peter Simonyi
Daniel Stenberg
Csoregi Natalia
Bogdan Tara
Jay Lim
Chris H-C
Rob Wu
Hiroyuki Ikezoe
Julian Descottes