These were papered by the call in HTMLFormElement that I removed in the
previous patch, which isn't necessary.
Caught by custom-elements/form-associated/ElementInternals-validation.html
The aTrack parameter is no longer required because, as of
https://phabricator.services.mozilla.com/D198231, MediaStreamRenderer no
longer needs the promise to be rejected when the track is destroyed.
Instead the wait for the device to start is terminated when no outputs to the
specified device remain.
NotifyWhenDeviceStarted() is removed from some gtests that don't have any
track outputs. They use WaitFor(cubeb->StreamInitEvent()) to wait for a
device anyway and don't need to know precisely when the graph switches from
the fallback driver to the callback. If a test does need this precise timing
it can use NotifyWhenDeviceStarted() if MediaTrack::AddAudioOutput() is used.
Differential Revision: https://phabricator.services.mozilla.com/D198232
Automatic update from web-platform-tests
[css-anchor-position] Implement new inset-area proposal
The new proposal is here:
https://github.com/w3c/csswg-drafts/issues/9598#issuecomment-1836854109
inset-area now affects the containing block size and 'auto' insets
become 0 for inset-area.
Bug: 1477314
Change-Id: Ia2f0d5a1f866cd659f9e3f87ec2f639141df6a94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5163733
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1247073}
--
wpt-commits: e359a0b5d78e0a5c221dcbd2a505e499d3cae178
wpt-pr: 43936
Automatic update from web-platform-tests
Rewrite prerender-while-prerender.html with a different technique
This test is flaky, and it's unclear whether it's because of a test bug or an implementation bug.
To try to rule out a test bug, rewrite the test to use fewer layers of abstraction. The resulting test is uglier and spread out over 4 files instead of 1. But, it should be very deterministic.
Bug: 1517319, 1402608
Change-Id: I2cf9939b58f7758f83dc051733abf0b2378c8d3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5197217
Auto-Submit: Domenic Denicola <domenic@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1247052}
--
wpt-commits: 204f186adf07940aa4296df2c18bbcb9241e3967
wpt-pr: 43993
Automatic update from web-platform-tests
Move webrtc-encoded-transform tests that are not aligned with the spec to a tentative folder (#43969)
* Move webrtc-encoded-transform tests that are not aligned with the spec to a tentative folder
--
wpt-commits: 82a5e64aeaba97eb26de0a999abcd983862e4143
wpt-pr: 43969
Automatic update from web-platform-tests
[text-spacing-trim] Implement line-end logic
This patch implements the line-end logic of `text-spacing-trim`
by applying the kerning only if it would not fit, as per the
resolutions at:
* https://github.com/w3c/csswg-drafts/issues/9521
* https://github.com/w3c/csswg-drafts/issues/9736
Bug: 1463891
Change-Id: I7b5b2ae43f47ce13c6eaad55a973292e82cc264f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5191602
Auto-Submit: Koji Ishii <kojii@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1246972}
--
wpt-commits: 05918d61fbde7aee1ffaf7211be717eed86f6c5a
wpt-pr: 43987
Automatic update from web-platform-tests
Add META.yml to mediacapture-insertable-streams folder and add some reviewers (#43971)
--
wpt-commits: e926548e859f4afd8f612254715051957cfdc68d
wpt-pr: 43971
Automatic update from web-platform-tests
Fix content-visibility-095.html expectation
This test seems to be working, except that the reference image doesn't
apply `contain: content` to the table corresponding to table.hidden,
which has content-visibility:hidden.
Bug: 1510865
Change-Id: I3beb913ad7910f983aec15c262d06e282006e063
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5195268
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1246889}
--
wpt-commits: 5049a31d2a7eebd7bca08317e56664021a8bd36c
wpt-pr: 43983
Update imports to use FOLDER/index, instead of relying on nodeJS
require behavior (which will look for the index file when importing FOLDER)
Differential Revision: https://phabricator.services.mozilla.com/D198423
Also remove devtools/client/debugger/src/utils/editor/source-editor.js which wasn't
used an look like a relic of ancient times.
Differential Revision: https://phabricator.services.mozilla.com/D198409
After D198523, NS_BLOCK_FLOAT_MGR and NS_BLOCK_MARGIN_ROOT are always
set simultaneously when initiating a frame, so we can merge them into a
single NS_BLOCK_STATIC_BFC flag. The freed bit is used to define a new
NS_BLOCK_DYNAMIC_BFC flag that has the same effect and is now used for
frames with paint/layout containment so that in D197043 they can be
updated later without having to reconstruct the frame tree. Finally
NS_BLOCK_BFC_STATE_BITS is the bitwise union of these BFC flags.
The following changes are made and cause no behavior changes:
- Instead of testing whether NS_BLOCK_FLOAT_MGR or NS_BLOCK_MARGIN_ROOT
is set, or whether all of the bits from
NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS are set, we test whether any
of the NS_BLOCK_BFC_STATE_BITS is set.
- Instead of adding NS_BLOCK_FORMATTING_CONTEXT_STATE_BITS when
constructing a frame, we add NS_BLOCK_STATIC_BFC. The exception is
for frame with paint/layout containment, for which we set
NS_BLOCK_DYNAMIC_BFC instead.
Differential Revision: https://phabricator.services.mozilla.com/D198530
Emilio Cobos Álvarez
Gregory Pappas
Mark Banner
Florian Quèze
Valentin Gosu
Karl Tomlinson
Iulian Moraru
moz-wptsync-bot
Rune Lillesveen
Kent Tamura
Domenic Denicola
youennf
Matthieu Dubet
Koji Ishii
Mason Freed
Nicolas Chevobbe
mcarare
Frédéric Wang
Mozilla Releng Treescript
Harshit Sohaney
Mike Hommey