Thunderbird releases come from the comm-esr.* repositories rather than the
comm-release repository. This adds a special case for Thunderbird and sets
the branch URL correctly.
This initial patch is based on the branch_prefix (comm or mozilla).
Differential Revision: https://phabricator.services.mozilla.com/D6509
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsAdd headless mode for chrome_webdriver (#13201)
0200c63a74a540dfb870881d5f476280c367d1c1 failed to add this to
chrome_webdriver, so add this now.
--
wpt-commits: 1e7408fcd394b66234c38c24ba044ec6f00e4b70
wpt-pr: 13201
Automatic update from web-platform-tests[css-properties-values-api] Substitution behavior.
Currently, registered properties substitute into other values exactly
like specified (like unregistered properties). This means that, for
a <length>-registered property with a specified value "10em" (for
instance), when that property is substituted via var()-reference,
the tokens "10em" are inserted. This is not correct, and produces the
wrong result with e.g. inherited values.
This CL changes that, by implementing "absolutization" of registered
custom properties: a process which calculates the computed value of
the property, and then produces a token stream usable for substitution
which is equivalent to the computed value.
* Currently we resolve var()-references on all custom properties
before applying high-priority properties. This is no longer
possible, because the true value of a custom property (also
unregistered) can not be known until the font has been updated.
Consider: --reg-len: 1em; --unreg:var(--reg-len). Here, the
computed value of --unreg should be "16px" (assuming a font-size
of 16px), and not "1em". If we destructively resolve --unreg
before the font size is known, we end up with the wrong tokens.
Hence the resolution process has been moved to after the font
has been updated.
* Custom properties must also be usable from high-priority properties.
Since they are no longer resolved beforehand, they are resolved
"on the fly", non-destructively. "Non-destructively" means that
resolved token streams are not stored on ComputedStyle, such that
any var()-references are kept for the _real_ resolution pass after
the font has been updated.
This works, because the high-priority properties do not require
proper "absolute substitution" to produce the correct value.
Note that font-size is special, in that font-relative units may
not be used if they arrive via a registered custom property.
* There is a special resolving pass for registered custom properties
(ComputeRegisteredVariables). This pass produces non-absolute CSSValues
for calculation of animation.
* Parsing of registered properties now happens entirely in
CSSVariableResolver, and no longer in variable.cc. Having this in
multiple places is just confusing.
R=futhark@chromium.org
Bug: 641877
Change-Id: Ic705d0808ffcea0ae5db02fb20870767175bb706
Reviewed-on: https://chromium-review.googlesource.com/1240274
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593902}
--
wpt-commits: c801e269e3e22d11e1bb4530ff15e87db877b1d2
wpt-pr: 13193
Automatic update from web-platform-testsFix firefox find_binary_path to accomodate channels
Firefox find_binary_path returned None since browser-channels were introduced
due to path differences. This fixes the same, along with a minor change to the
Nightly path on Mac as it contains a space.
The default for |wpt run firefox| without a channel specified is set to nightly,
along with a log message when this happens.
--
wpt-commits: f3a1f9324097311cafcd7893066e3e40fe172fd0
wpt-pr: 13185
Automatic update from web-platform-testsAdd interface tests for TransitionEvent
These are modelled after the similar tests that exist for AnimationEvent
in css/css-animations, except written using more modern WPT style.
Bug: 695504
Change-Id: I63573cf48aba6821f5e22486ef18217d0f2828ee
Reviewed-on: https://chromium-review.googlesource.com/1239457
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593620}
--
wpt-commits: b040cb2a07264d35b9f47cd9deb2fb2889fca6d4
wpt-pr: 13168
Automatic update from web-platform-tests[PE] Fix fragment clip and paint offset under multicol vertical-rl scrolled
The previous code in VisualOffsetFromPaintOffsetRoot() converting the result
into scrolling contents space used ScrolledContentOffset which mismatched
the new ScrollTranslation which also includes scroll origin. Now use
ScrollTranslation instead.
Also removed the wrong remedy about scroll origin in one of the callers.
Bug: 887423
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I9a72ed6ddc066c5b4c9970037ed4c4287c5a2f0f
Reviewed-on: https://chromium-review.googlesource.com/1239170
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593572}
--
wpt-commits: 68d63d516e6bc4b83934d71616b2aa82d8efe2af
wpt-pr: 13157
Automatic update from web-platform-tests[css-grid] Performance optimizations in the Baseline alignment code
Since we integrated the baseline alignment logic in the grid tracks
sizing algorithm, its impact on performance has grown considerably.
The analysis of the new logic added and its overhead, due to different
operations, shows that evaluating the item's participation in the
baseline alignment context is the most expensive one. It's specially
demanding the evaluation of the grid item's alignment properties.
Considering that currently we are doing this for every grid item, this
CL propose to reuse the loop we already have to clear the grid item's
override size to cache the items with a baseline value in their
alignment CSS properties.
Thanks to this cache we can determine the item's participation in a
baseline alignment context in the different phases of the track sizing
algorithm, with almost no cost (compared to the current logic). It may
be possible to share the cache with the algorithm run for computing the
grid's intrinsic size; however, if the intrinsic size logic is run
before the grid's layout, we'll end up duplicating the cache.
Additionally, this cache is also used in the alignment phase of the
grid layout logic; this change helps to avoid the various issues we
have been suffering related to the different evaluations of the item's
participation in baseline during the different phases of the grid
layout algorithm.
BUG = 873452
Change-Id: Ida27be11ae0f5c455e6077367a277981ab35cec1
Reviewed-on: https://chromium-review.googlesource.com/1179897
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#593552}
--
wpt-commits: f6de5f7d5d50b1ad30a1e17922e183868fd3e935
wpt-pr: 12816
Automatic update from web-platform-testsAdd a headless mode command line option (#13076)
For browsers which support headless mode starting wptrunner with
--headless will run the tests in headless mode; otherwise it will be
ignored.
--no-headless is avaiable to explicitly disable the mode when
frontends change the defaults.
For firefox switch the default for wpt run to be headless; for Chrome
changing the default broke some smoketests, so don't switch until that
is resolved. In all cases continue to run in a normal windowed mode in CI.
--
wpt-commits: 0200c63a74a540dfb870881d5f476280c367d1c1
wpt-pr: 13076
Automatic update from web-platform-testsVisual change on background-clip changes.
The background-clip property affects background-color visually, so we
need to say a layer is visually different even without an image.
We had a wpt test for this which had a stray line which made the test
always pass.
Bug: 887350
Change-Id: Icc585f9e631485970b6509e015eff1e2007e4f0b
Reviewed-on: https://chromium-review.googlesource.com/1238448
Reviewed-by: Anders Ruud <andruud@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593523}
--
wpt-commits: 00c1fd9ea4bc1e03f966919f1e209ab8cd81f57e
wpt-pr: 13187
Automatic update from web-platform-testsFix some tests in test_request.py for python 3. (#11757)
--
wpt-commits: 61e09bec3d21b4e9137dadafc20c04cb9be7ce3e
wpt-pr: 11757
Automatic update from web-platform-testsUpdate mozrunner from 7.0.0 to 7.0.2 (#13167)
--
wpt-commits: 91491deb7dcfe4a0d0ece61f086345abad4d46a4
wpt-pr: 13167
This ensures that we always start from a partial manifest where possible and also ensures that the
configuration files are correctly created (a refactor to create these irrespective of whether we
do a download would make sense, but this fixes the immediate problem)
Depends on D7088
Differential Revision: https://phabricator.services.mozilla.com/D7089
Usually this directory is created by the build system. However if we
run ./mach wpt-manifest-update before trying to do a build it can
error out. Just creating the directory should be enough to fix this.
Differential Revision: https://phabricator.services.mozilla.com/D7088
Otherwise it doesn't work with multiprocessing, which breaks debugging wpt on Windows.
Differential Revision: https://phabricator.services.mozilla.com/D7173
--HG--
extra : moz-landing-system : lando
These regexes are used for things like determining which tasks to run given a
"path" int |mach try|. Previously, we used patterns like:
mochitest-chrome-(?:e10s)?(?:-1)?$
This would match both e10s and non-e10s versions of a task with either no
chunks, or only selecting chunk 1. But we keep adding other configurations, e.g
-gpu, -no-accel, -sw, etc. Each time we create a new possibility we need to
remember to update these task regexes (or else lose test coverage when using
paths with |mach try|).
Instead of individually listing every possibility, let's use a pattern like
this:
mochitest-chrome($|.*(-1|[^0-9])$)
This also selects tasks that are either chunk 1 or don't have any chunks. But
it allows for arbitrary strings in-between. This regex doesn't need to be
updated when we add configurations like -sw.
Depends on D7119
Differential Revision: https://phabricator.services.mozilla.com/D7120
--HG--
extra : moz-landing-system : lando
I almost forgot to update the regexes in moztest.resolve when creating the -sw
variant of task. This adds a test to make sure we don't forget more things in
the future.
Differential Revision: https://phabricator.services.mozilla.com/D7119
--HG--
extra : moz-landing-system : lando
The patch c1df1c2e46f6 contained a faulty rebase where the coercion
of logging::max_level() changed from the Pref type to a string.
The string representation of geckodriver::logging::Level is given
in upper-case, e.g. "INFO", and the Pref representation is given as
"Info" to be compatible with managing the log level from Log.jsm in Gecko.
This inadvertently caused
https://github.com/web-platform-tests/wpt/issues/12166 to reappear
in almost the same way: before the problem was that Marionette’s
frame script always included all log level entries. This was fixed
with https://bugzilla.mozilla.org/show_bug.cgi?1482829, but then
https://bugzilla.mozilla.org/show_bug.cgi?id=1396821 broke it so
that log entries also from chrome space appeared.
Depends on D7077
Differential Revision: https://phabricator.services.mozilla.com/D7078
--HG--
extra : moz-landing-system : lando
mozprofile gives us an error and we can forward it to the user so
we know what the underlying reason is for not being able to write
the Firefox profile.
Depends on D7075
Differential Revision: https://phabricator.services.mozilla.com/D7076
--HG--
extra : moz-landing-system : lando
Done automatically by running MarionetteHandler through rustfmt(1).
Depends on D7074
Differential Revision: https://phabricator.services.mozilla.com/D7075
--HG--
extra : moz-landing-system : lando
PrefValue implements From<&'static str>, and this makes the calling
code slightly nicer to look at.
Differential Revision: https://phabricator.services.mozilla.com/D7074
--HG--
extra : moz-landing-system : lando
The refactoring of the webdriver crate to use Serde (bug 1396821)
caused this regression. By instructing Serde to correctly rename
both properties fixes it.
Differential Revision: https://phabricator.services.mozilla.com/D7079
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsUpdate marionette_driver from 2.6.0 to 2.7.0 (#10805)
--
wpt-commits: 23c54943daee3cd8520a6d86acc055f1120f96ad
wpt-pr: 10805
Automatic update from web-platform-testsVarious test fixes for python3 support. (#11769)
--
wpt-commits: 5bd512cdc76f762662915a2d3d9e49b021f14ff6
wpt-pr: 11769
Automatic update from web-platform-testsRemove WebKitAnimationEvent
This is an obsolete prefixed alias of AnimationEvent. An
intent-to-remove has been sent, and has got LGTM*3.
Blink intent thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/EgMUDqySZwE
Bug: 695504
Change-Id: Ia86e830fe3f653aa6a7b2f983afb75fd4d088831
Reviewed-on: https://chromium-review.googlesource.com/1238497
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Tim Volodine <timvolodine@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593405}
--
wpt-commits: 1c99c70996f35332b8a65040bf745f19678a6686
wpt-pr: 13149
Automatic update from web-platform-tests[testharness.js] Remove deprecated API (#12976)
[testharness.js] Remove deprecated API
The testharness.js functions `assert_exists` and `assert_not_exists`
have been labeled "deprecated" since 2012-01-31 [1]. Remove the
functions and replace all existing references with equivalent
assertions.
[1] 1780607fc4582b65b7fcdded3e39e79e95c8d915
--
wpt-commits: efa1c1e224cf7910008d37477beb954d41448ace
wpt-pr: 12976
Automatic update from web-platform-testsMake is_html actually work in Output#resolve_log().
In particular, is_html would never become true if SVGSVGElement was supported
at all.
Even if SVGSVGElement was not supported, it would never become true because
we were checking the namespace and localName of the Document object, rather
than the root element.
--
wpt-commits: 7f3e17fe6d5d48b0090b7b176fa5175037580654
wpt-pr: 13121
Automatic update from web-platform-testsUpdate selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.13.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
wpt-commits: fab6e8e35344dc06267d1ba5a75780d0e0f3a6fc, ee8755b0f6cdaf901cf04c35a862070036e2df69, bc3d67c0658a7dd890c72c6bb896476014b65889, 3328d27dd5c1218c541baf9fd52cc981761867c8, 90d366cb68e06d42022f32065a568190b014a5fd, f5de401ce433e130cd2d1d015697bed544cf8654, 24c572a0727f8b2fe193b84024288b4b51bb3cef
wpt-pr: 13133
Automatic update from web-platform-testsCheck if platform is Windows before catching WindowsError
Check if the platform is Windows and the error is a WindowsError before
trying to run git.bat, as WindowsError is not defined in non-Windows.
Closes https://github.com/web-platform-tests/wpt/issues/12693
--
wpt-commits: 82d852bda1e08948858389c17402fa0571bc2584
wpt-pr: 13177
Automatic update from web-platform-testsAlso ignore ERROR in slow test check
Tweak the docstring accordingly to explain why.
--
wpt-commits: 130669061c6f4b475e1189ef107010966d686324
wpt-pr: 13158
Automatic update from web-platform-tests[wptrunner] Fix support for `--binary-arg` in Fx (#13154)
In order to automate Firefox, wptrunner requires the browser's internal
module "Marionette" to be enabled. This is a requirement regardless of
any custom configuration specified by the user, including additional
command-line flags via the `--binary-arg` argument.
Previously, this project would omit the `-marionette` argument in the
presence of any user-specified arguments. Because this interferes with
normal operation (and because the source code is formatted in a way that
conflicts with the order of operations), this is likely an unintentional
behavior.
Modify the code which derives the command-line arguments to always
include the `-marionette` argument.
--
wpt-commits: 3a749a13168916563b9611528b18d0376f04aab1
wpt-pr: 13154
Automatic update from web-platform-testsMerge pull request #13179 from yoavweiss/multiple_wildcard_test
[resource-timing] Add TAO test for multiple wildcards
--
wpt-commits: 3d117ae1266e6bd039a3a1ab92b27e82c3ccc92d
wpt-pr: 13179
Automatic update from web-platform-testsUnbreak html/dom/interfaces.https.html
This change makes /interfaces/touch-events.idl get fetched, rather
than /interfaces/touchevents.idl (which doesn't exist).
--
wpt-commits: 5d58e091e71aa3162fe9d0e40858351c8063ca08
wpt-pr: 13172
Automatic update from web-platform-tests[service-workers] Return value in cleanup (#13163)
Previously, many tests un-registered service workers using the
testharness.js API `add_cleanup` without returning the promise which
tracked the operation. While this ensured the operation was started at
the completion of the test, it did not guarantee that the operation
would be completed before the test was considered "complete."
In automation scenarios where many tests are executed in rapid
succession, this enabled a race condition: the navigation could
interrupt the un-registration process. In order to account for the
possibility of registrations that persisted from previous test failures,
the tests included "setup" code to defensively un-register such workers.
The `Test#add_cleanup` method was recently extended to support
asynchronous "clean up" operations [1]. Use that API to ensure tests are
not considered "complete" until after service worker un-registration is
done.
[1] https://github.com/web-platform-tests/wpt/pull/8748
--
wpt-commits: 7897f9d5beff624590d2fc254d2a7eca6e2b1e8f
wpt-pr: 13163
Automatic update from web-platform-testsMerge pull request #13159 from web-platform-tests/fix-mplus-1p-regular
Fix the path of mplus-1p-regular.woff in all tests
--
wpt-commits: eb68211270c6deb66eb928799a75e6af3b8db1b0
wpt-pr: 13159
Automatic update from web-platform-testsFix scrollIntoView(...) for SVG elements
AbsoluteBoundingBoxRectForScrollIntoView and associated helpers did not
compute the correct bounding box for SVG shapes (or anything but the SVG
root.)
Compute the bounding rect using the stroke bounding box.
Bug: 803440
Change-Id: If25ca98b686f17a0db699e569460cb4c276f06a0
Reviewed-on: https://chromium-review.googlesource.com/1238458
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#593306}
--
wpt-commits: b3ca0cee4b0772e615334e4155556ec254dab7b1
wpt-pr: 13145
Automatic update from web-platform-tests[css-layout-api] Move perform-child-layout tests to child-constraints
As above, move similar tests into subdirectory, and apply minor
documentation cleanups.
Adds two new tests checking that setting an invalid (negative) available
size, clamps it to zero.
Bug: 726125
Change-Id: Id5bdfa25970a4e4bfe359377b88176043ab1f6c3
Reviewed-on: https://chromium-review.googlesource.com/1236266
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593236}
--
wpt-commits: 80fa83f6ca3dc7039088afae9a908222b31f6aa4
wpt-pr: 13130
Automatic update from web-platform-tests[css-layout-api] Adds ability to specify percentage{Inline,Block}Size.
This allows developers to specify the size which percentages in the
block (wrt child writing mode) direction should be resolved against.
Currently inline percentages still resolve against the available
inline-size.
This adds a "OverrideContainingBlockPercentageResolutionLogicalHeight"
field on layout box, which both the logic for
LayoutBox::ComputePercenatgeLogicalHeight and
LayoutBox::ComputeReplacedLogicalHeight use.
They follow similar logic to LayoutGrid, in that in quirks mode,
percentages are treated as indefinite (doesn't "walk-up" the tree).
Change-Id: I256381687d2eed7693a908074f7f5032d5963e2b
Reviewed-on: https://chromium-review.googlesource.com/1232206
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593208}
--
wpt-commits: 159da2f8ef7c8259c7fc013cbfea2314e2dfdeeb
wpt-pr: 13124
Automatic update from web-platform-tests[css-properties-values-api] Use inherited value for substitution.
When a var()-reference produces tokens that are incompatible with the
current syntax, or the var()-reference refers to a variable that does not
exist, we currently always substitute the initial value, even for
inherited properties. This is incorrect, as the value should behave as
'unset', which means 'inherit' for inherited properties.
Note that if syntax-incompatible tokens are specified directly (not via a
var()-reference), we correctly behave as 'unset'. This is because the
var()-less case is handled by a different code path (variable.cc).
R=futhark@chromium.org
Bug: 641877
Change-Id: Ifdd5435ee77f4b8cd3998967713cb6fcb7e8d5f4
Reviewed-on: https://chromium-review.googlesource.com/1235579
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593145}
--
wpt-commits: 689968f390a8c5c897ab5c9fa0f6fe27a40b5cc3
wpt-pr: 13120
Automatic update from web-platform-testsDon't try to parse the contents of server errors in idl_test().
--
wpt-commits: af65cfb6db68e2b3255290ce8ec362376eb44efa
wpt-pr: 12870
Automatic update from web-platform-testsAdd pictureInPictureWindow to enterpictureinpicture event.
This makes sure web developers can access to the PictureInPicture window
object when user agent initiates Picture-in-Picture. It does so by
adding a pictureInPictureWindow attribute to the existing
enterpictureinpicture event
Intent to ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/ibVPbqBQapU/Fgf307XJBgAJ
Change-Id: I46ce1f4047b670f49dd746e39c7e62efc1b4a135
Bug: 887856
Reviewed-on: https://chromium-review.googlesource.com/1228122
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593127}
--
wpt-commits: 33a9abd00e4a5169cb75ad6c32bb744b85027a0a
wpt-pr: 13048
Automatic update from web-platform-testsbindings: Implement timers with V8Function
This fixes bug 866610 by using the IDL infrastructure to properly enter
the v8::Context before calling the registered callback.
Also ensure eager finalization of ScheduledAction in DOMTimer to
prevent a memory leak. Added two more effective DCHECKs to confirm.
Bug: 866610
Change-Id: I37d7bd05f035fe31856cfe68bae51aa0632cd3b1
Reviewed-on: https://chromium-review.googlesource.com/1220486
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Timothy Gu <timothygu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593108}
--
wpt-commits: 4eaebdf70cbbbac6b95d757c424a879c1f980dac
wpt-pr: 13012
Automatic update from web-platform-tests[css-masking] Inheritance and initial values (#13094)
Test that CSS Masking properties inherit.
Test their initial values match the spec.
https://drafts.fxtf.org/css-masking-1/#property-index
--
wpt-commits: f0ef29b3f9d01cd3278fdaef67c323370a3a8f72
wpt-pr: 13094
Automatic update from web-platform-tests[css-writing-modes] Inheritance and initial values (#13093)
Test that CSS Writing Modes properties inherit.
Test that initial values match the spec.
https://drafts.csswg.org/css-writing-modes-3/#property-index
--
wpt-commits: 90e5630bfa70bc56a450c4584f44846ccc123d88
wpt-pr: 13093
Automatic update from web-platform-tests[css-break] Inheritance and initial values (#13092)
Test inheritance and initial values of properties
defined by CSS Fragmentation.
https://drafts.csswg.org/css-break/#property-index
--
wpt-commits: e441850483b6f68a7335ee69920f5d7758e89bef
wpt-pr: 13092
Automatic update from web-platform-testsRevert "Revert "[css-tables] Force layout when colgroups are removed or added""
Fixes an uninitialised variable caught by MSAN.
This reverts commit 66a74d2f7e1b369ce086c3c41ee089d72f3d0018.
Change-Id: I1e896476fe201fb05072970220bab5c3b20588a2
Reviewed-on: https://chromium-review.googlesource.com/1233746
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592938}
--
wpt-commits: a25aa4b1f3ef9011ee30ecffe7203157d72ae5ae
wpt-pr: 13077
Automatic update from web-platform-tests[css-shapes] Inheritance and initial values (#13068)
Test that CSS Shapes properties are not inherited.
Ttest the initial values match the spec.
https://drafts.csswg.org/css-shapes/#property-index
--
wpt-commits: 9f97edb27e139e3ceda1b234016151170bd41172
wpt-pr: 13068
Automatic update from web-platform-testsMerge pull request #13063 from ewilligers/contain-inheritance
[css-contain] Inheritance and initial value
--
wpt-commits: 7930fceb0110a8309e39fcbc34b6ef6a5d4f583e
wpt-pr: 13063
Automatic update from web-platform-testsMerge pull request #13060 from ewilligers/display-inheritance
[css-display] Inheritance and initial value
--
wpt-commits: 479f20992ddd32505d130c9a140844dc8228c3c7
wpt-pr: 13060
Automatic update from web-platform-testsUse NotFoundError instead of InvalidPointerId
This cl follows the new pointerevent spec which
uses more common WebIDL specified exception
NotFoundError instead of defining new
InvalidPointerId exception.
Bug: 885321
Change-Id: I28e946ffcb96c9fb4f70c76a4b9c09be620f981d
Reviewed-on: https://chromium-review.googlesource.com/1231990
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Ella Ge <eirage@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592903}
--
wpt-commits: c73ea25fec2bcede3bb0f622c4b9fc5076e7ff62
wpt-pr: 13059
Automatic update from web-platform-testsMerge pull request #13131 from Loirooriol/css-computed-insets-fix
Fix syntax and typos in tests from #12956
--
wpt-commits: 6718d7d67d65a2d3073bd29783f4ec6b76d47be8
wpt-pr: 13131
Automatic update from web-platform-testsUpdate doc regarding exp. features on Chrome
Following https://github.com/web-platform-tests/wpt/pull/13011, `wpt`
automatically turns on experimental web platform features on Chrome if
the channel is "dev". Update the doc to reflect this change.
--
wpt-commits: b0ea10809d150e8492bb20df51583e16a2f4f1ac
wpt-pr: 13129
Automatic update from web-platform-tests[service-workers] Refactor tautological tests (#13043)
* [service-workers] Refactor tautological tests
Previously, these tests created Promise values which would be fulfilled
even when expectations were violated. This would cause the test harness
to interpret them as "passing" regardless of implementation status.
Remove the use of `Promise.prototype.catch` to ensure that promise
rejections which occur during test execution lead to test failure.
--
wpt-commits: 3411e4bff0a7c875811e65398472cc6403619476
wpt-pr: 13043
Automatic update from web-platform-tests[docs] Remove obviated instructions
As of [1], the WPT CLI automatically inserts the
`--use-fake-ui-for-media-stream` and
`--use-fake-device-for-media-stream` arguments for the Chrome browser.
[1] a4eaa46ffebe5785562b930316a300423f23707e
--
wpt-commits: 70ca025c50fb6dc3b2f828de062e412d7897daf8
wpt-pr: 13126
