Previously we had no way from excluding just one channel from TRR mode3.
The solution was to add the captive portal domain to the exclusion list.
Now the captive portal channel is marked with nsIRequest.DISABLE_TRR_MODE so
the exclusion is not necessary anymore.
Differential Revision: https://phabricator.services.mozilla.com/D48820
--HG--
extra : moz-landing-system : lando
* Makes it possible to selectively enable TRR for pbmode/container/window/etc
Differential Revision: https://phabricator.services.mozilla.com/D48363
--HG--
extra : moz-landing-system : lando
The forced garbage collection has been added a decade ago for a test that
exhibited a memory increase over time in Firefox. Now that the test is no
longer present in the tree, and the garbage collector got a lot of improvements
over the last years, there is no compelling reason to keep the call to
"forceGC()" in the closing handler of httpd.js.
Differential Revision: https://phabricator.services.mozilla.com/D58550
--HG--
extra : moz-landing-system : lando
Until the underlying issue has been identified on bug 1606684 keep running
a forced GC to clean-up any internal references to temporary XPI files.
Differential Revision: https://phabricator.services.mozilla.com/D58549
--HG--
extra : moz-landing-system : lando
Throw error if the wrapped WeakRef is a dead wrapper.
Also do the checking earlier so we can bail out early before setting the
target slot.
Differential Revision: https://phabricator.services.mozilla.com/D58522
--HG--
extra : moz-landing-system : lando
Easy to miss that the slow formatting code is run unconditionally.
The remaining instances are in recording and startup code.
Differential Revision: https://phabricator.services.mozilla.com/D58920
--HG--
extra : moz-landing-system : lando
In media/mtransport/third_party/nICEr/src/stun/addrs.c:
stun_getifaddrs() is used on all non-WIN32 targets. It extracts from the
kernel an array describing network interfaces (I think). These are written
into its out-parameter nr_local_addr addrs[] and the number of entries is
written to int *count.
There is a path through the main loop in stun_getifaddrs() which can cause a
nr_local_addr record to be returned with its .interface.type field being
uninitialized, but which nevertheless is later used. It also looks as if the
.interface.estimated_speed field is not initialised.
This commit zero-initialises the entire output array before writing anything
into it, to avoid such problems, on all targets.
Differential Revision: https://phabricator.services.mozilla.com/D58822
--HG--
extra : moz-landing-system : lando
This adds support for holes within virtual surfaces. On platforms
that don't use virtual surfaces, this just works by destroying
the tile that is empty so it never gets composited.
Differential Revision: https://phabricator.services.mozilla.com/D59059
--HG--
extra : moz-landing-system : lando
- Cleaned up some comments.
- Changed some const nsACString& parameter types to nsCString to accept r-value
and l-value nsCStrings.
Differential Revision: https://phabricator.services.mozilla.com/D58877
--HG--
extra : moz-landing-system : lando
Add a script block to prevent reflow observers from running the scripts,
which may flush layout, until the end of DidDoReflow().
Specifically, Document::MaybeInitializeFinalizeFrameLoaders() can flush
layout somewhere down in the stack as bug 1606492 comment 0 shows.
Adding a script block can force it to schedule its runnable to run at
the end of DidDoReflow().
Also, HandlePostedReflowCallbacks() can flush layout. It's better to check
`mIsDestroying` before proceeding.
Differential Revision: https://phabricator.services.mozilla.com/D59015
--HG--
extra : moz-landing-system : lando
Nowadays, ColumnSetFrame is an inner frame under ColumnSetWrapperFrame.
It always has "block-size: auto", so `aReflowInput.ComputedBSize()`
always equals to NS_UNCONSTRAINEDSIZE.
Also, -moz-column-content no longer has "max-block-size: 100%", so
NS_FRAME_CONTAINS_RELATIVE_BSIZE can never be set on ColumnSetFrame when
constructing ReflowInputs for ColumnSetFrame's children in
`ReflowInput::InitResizeFlags`. Removing the bit is not needed, either.
Differential Revision: https://phabricator.services.mozilla.com/D58732
--HG--
extra : moz-landing-system : lando
Simply remove "max-block-size: 100%" for -moz-column-set and
-moz-column-content breaks abspos-breaking-dynamic-{001,002,003}.html.
We need to reflow ColumnSetWrapper's children whenever
ColumnSetWrapper's block-size or max-block-size is changed because both
size affect the available block-size for ColumnSetWrapper's children.
We set `NS_FRAME_CONTAINS_RELATIVE_BSIZE` for ColumnSetWrapperFrame so
that it will set itself dirty in `selfDirty` in
`nsBlockFrame::ReflowDirtyLines`, and mark its lines dirty if
`aState.mReflowInput.IsBResize()` is true.
Differential Revision: https://phabricator.services.mozilla.com/D58731
--HG--
extra : moz-landing-system : lando
Note that this also implicitly adds support for the view-source+srcdoc configuration, and setting of the BaseURI, which were both in the nsDocShell version but not the others.
Differential Revision: https://phabricator.services.mozilla.com/D57887
--HG--
extra : moz-landing-system : lando
It's possible that `self` is the last pointer holding the media cache, so we have to ensure releasing `self` on main thread because media cache should always be destroyed on main thread only.
Differential Revision: https://phabricator.services.mozilla.com/D58900
--HG--
extra : moz-landing-system : lando
Now that we have UTF8String in the WebIDL, we can remove quite a few of the
conversions. Do that, and lift the remaining string conversions up as needed.
Also deindent Servo_ComputeColor while touching it.
Most of the remaining copies are because either bug 1606994, or because they're
WebIDL attributes that we still need to serialize back as UTF-16 (bug 1606995).
Differential Revision: https://phabricator.services.mozilla.com/D58687
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
HTML: attempt to make COEP test less flaky
Hopefully addresses https://bugzilla.mozilla.org/show_bug.cgi?id=1605382.
--
wpt-commits: e8fdcbaf22bf28238bb126d84bc960fe9625fe02
wpt-pr: 21021
Automatic update from web-platform-tests
[webnfc] Add several wpt tests
This CL adds several wpt tests for Web NFC:
- Test push operation fails when data transfer fails
- Verify pushed message for empty record type
- Test reading message with multiple records should succeed
Bug: 520391
Change-Id: Iadb13f6cebaf30514ba7bef65a69302b368e4359
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982271
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Leon Han <leon.han@intel.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#728434}
--
wpt-commits: 3488a5a845bec08943f66974e9f0df4ffe96774a
wpt-pr: 20921
Automatic update from web-platform-tests
Revert LayoutInline::CollectLineBoxRects
This patch reverts |LayoutInline::CollectLineBoxRects| not to
use |NGInlineCursor|, by manually merging parts of r706815
<crrev.com/c/1862534> and r710694 <crrev.com/c/1888624>.
|NGInlineCursor| is rapidly changing that reverting is not
easy. This patch reverts not to use it for |getClientRects|
and a few other callers.
Testing more on culled inline box indicates that the phase 1
of LayoutNG regressed some cases from legacy, and
|NGInlineCursor| work regressed further. We might want to fix
when NGFragmentItem ships, but better not to change the
behavior until then.
Bug: 1036358
Change-Id: I47a60f5d3a505d4b43eba0d8b5adc64e02cbcd28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971632
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728433}
--
wpt-commits: 280816c7465a6593f06f9f5651a70eb857f9f774
wpt-pr: 20892
Automatic update from web-platform-tests
Fix validity.valueMissing tests (#21031)
These changes fix expectations for validity.valueMissing and validity.valid for disabled/readonly textual elements. This fixes#21007.
--
wpt-commits: 31e82ba312dea8b0011237fd696d3c87c2015d65
wpt-pr: 21031
Automatic update from web-platform-tests
Use mozlog logger in FontInstaller
This is the right thing to do, and prevents a race where we try to log
after the stdout capture queue is closed
Differential Revision: https://phabricator.services.mozilla.com/D56567
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1598561
gecko-commit: 2a0e33dbb9c83f2444361497e86e7af7d69fef44
gecko-integration-branch: autoland
gecko-reviewers: maja_zf
--
Remove unused import
--
wpt-commits: fd7d1aaf7d490d8d0e9f039db02a530891112c5a, d24e7e551416c0adb313fd51070c6db4762949b8
wpt-pr: 20997
