Automatic update from web-platform-tests
Remove duplicated copies of 60x60-red.png file
Update paths to use the only copy that is kept under "/css/support/".
--
wpt-commits: 701892246be156a8a051083c9c50ab22a89a26a5
wpt-pr: 12818
Automatic update from web-platform-tests
Remove duplicated copies of 60x60-red.png file
Update paths to use the only copy that is kept under "/css/support/".
--
wpt-commits: 701892246be156a8a051083c9c50ab22a89a26a5
wpt-pr: 12818
Automatic update from web-platform-tests
Fix a bunch of broken paths to specs in tests (#22460)
--
wpt-commits: 5aa5889d7f2ba9cd60a83c1d39e1d852374f7879
wpt-pr: 22460
Automatic update from web-platform-tests
shape-outside test slightly incorrect (#22019)
* Parent container was too narrow for image, margin and text
* Tighter constraint
--
wpt-commits: 1f45266914e4397dbe715db8ba27ab30963be794
wpt-pr: 22019
Tweak the ShapeSourceRepresentation so that it doesn't store Option<>s.
Some renames so that GeometryBox doesn't conflict with the Gecko type, and some
other usual bits / re-exports to deal with cbindgen and generics.
Also, drive-by derive parsing of GeometryBox as it's trivial.
Doing this unfortunately is not possible without removing nsStyleImage first, so
let's do that before.
This makes us serialize in the shortest form for shape-outside, but that's what
we should do anyway.
(aside: the shapes code is a bit too generic, maybe we should unify
ClippingShape and FloatAreaShape...)
Differential Revision: https://phabricator.services.mozilla.com/D62163
--HG--
extra : moz-landing-system : lando
For now, we still bail out at the stage of getting the calc node into a
CalcLengthPercentage if we couldn't simplify the min() / max() / clamps()
involved.
After this plan is to use just CalcNode everywhere instead of
specified::CalcLengthPercentage, and then modify the computed
CalcLengthPercentage, which would look slightly different as we know all the sum
terms for those are a struct like { Length, Percentage, bool has_percentage } or
such, so all the simplification code for that becomes much simpler, ideally.
Or we could turn CalcNode generic otherwise, if it's too much code... We'll see.
Differential Revision: https://phabricator.services.mozilla.com/D61739
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add load method to protocol
--
Generalise reftest-wait script to allow other test types
--
Ad crashtest support to manifest
--
Add crashtest support to wptrunner
--
Add example test
--
Rename existing -crash tests that may not work as crashtests
For testharness tests the following criteria were applied:
* Test includes an assert
* Test includes something other than synchronous tests
For reftests all existing tests were renamed
--
Schedule crashtests in CI
--
Add some docs for crashtests
--
wpt-commits: c1954bcecd0991460d9f2b58456da8958cb97424, e8b454eebe22173569353ae3e327cd8a6951b9e0, cee68c9e85c0d3835f7e4ae3eb673f919242c881, 5a636f4de065dbd756f39b41859d378bd3609658, 14f8cfeb1458deb523f179cff1ae7b2bf12dc667, 50ae113e26987271de56826873c0a2eb43f7b515, 40113cc91c00f0cad78072d2fd51805a775df95c, 5b46ea7c4fe67113a69306afbf9c95b6ba041dbf
wpt-pr: 20017
--HG--
rename : testing/web-platform/tests/css/css-contain/contain-chrome-crash-001.html => testing/web-platform/tests/css/css-contain/contain-chrome-thcrash-001.html
rename : testing/web-platform/tests/css/css-images/gradient-crash.html => testing/web-platform/tests/css/css-images/gradient-refcrash.html
rename : testing/web-platform/tests/css/css-images/infinite-radial-gradient-crash.html => testing/web-platform/tests/css/css-images/infinite-radial-gradient-refcrash.html
rename : testing/web-platform/tests/css/css-pseudo/before-in-display-none-crash.html => testing/web-platform/tests/css/css-pseudo/before-in-display-none-thcrash.html
rename : testing/web-platform/tests/css/css-pseudo/first-letter-of-html-root-crash.html => testing/web-platform/tests/css/css-pseudo/first-letter-of-html-root-refcrash.html
rename : testing/web-platform/tests/css/css-shapes/shape-outside/supported-shapes/inset/shape-outside-inset-crash.html => testing/web-platform/tests/css/css-shapes/shape-outside/supported-shapes/inset/shape-outside-inset-refcrash.html
rename : testing/web-platform/tests/css/css-typed-om/set-var-reference-crash.html => testing/web-platform/tests/css/css-typed-om/set-var-reference-thcrash.html
rename : testing/web-platform/tests/dom/nodes/remove-and-adopt-crash.html => testing/web-platform/tests/dom/nodes/remove-and-adopt-thcrash.html
rename : testing/web-platform/tests/payment-request/payment-request-constructor-crash.https.html => testing/web-platform/tests/payment-request/payment-request-constructor-thcrash.https.html
rename : testing/web-platform/tests/svg/pservers/pattern-with-invalid-base-cloned-crash.html => testing/web-platform/tests/svg/pservers/pattern-with-invalid-base-cloned-thcrash.html
Automatic update from web-platform-tests
[css-shapes] Refactor tests (#19921)
testharness.js was recently extended with an API to explicitly opt-in to
the "single page test" feature [1]. As per WPT RFC 28 [2], tests which
do not use this API and which do not declare any subtests will soon be
reported as a harness error.
Update some tests which previously opted in implicitly to use the new
API. Update others to instead declare a single subtest (so that they are
no longer single-page tests).
[1] https://github.com/web-platform-tests/wpt/pull/19449
[2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
--
wpt-commits: e6c03912b75fe8b8aefeacc8814ae6e8a0c78679
wpt-pr: 19921
Differential Revision: https://phabricator.services.mozilla.com/D53506
Automatic update from web-platform-tests
Convert tabs to spaces in css/ directories with few lint errors (#19832)
This follows the same approach as in https://github.com/web-platform-tests/wpt/pull/19824
to identify directories in css/ with few lint errors and removes the
lint.whitelist exceptions for those.
For css/css-counter-styles/ some newlines were also added/removed to
arrive at a reasonable style.
--
wpt-commits: 5af91f79216344d5a243f2fc133e373b39e1322e
wpt-pr: 19832
Automatic update from web-platform-tests
Fixup a css-shapes test broken by #19577 (#19731)
--
wpt-commits: 88c0d6780f897eacd4783e1aaf0ff15756515530
wpt-pr: 19731
Automatic update from web-platform-tests
Load Ahem as a web font in css-shapes tests. (#19577)
This makes font setup/restoration explicit rather than per-subtest.
This allows us to setup Ahem usage, then wait for fonts to load, and
then run all computed tests as a discrete block.
The previous method (which dynamically inserted Ahem prior to a subtest
and removed it immediately after) didn't allow us to wait for the web
fonts to be loaded because the test page would have no Ahem usage
present at the time we waited for the fonts.ready event.
--
wpt-commits: 4c1bbd4b27cfa527485d4f56609895c9df55212b
wpt-pr: 19577
Automatic update from web-platform-tests
[cssom] getComputedStyle not getComputedValue (#17799)
Fix typo in test titles.
--
wpt-commits: 9daa6ffd6eb28afb0940b7ac304b08e8383fc527
wpt-pr: 17799
Automatic update from web-platform-tests
Load Ahem as a webfont everywhere (part 2) (#17173)
This change updates a large number of reftests to link to the
`/fonts/ahem.css` stylesheet. Each file contains a single additional
line before the first `<style>` element:
```
<link rel="stylesheet" type="text/css" href="/fonts/ahem.css" />
```
--
wp5At-commits: 9c780585758acf5e9ac6d17ad9bd03c83404c7e6
wpt-pr: 17173
Automatic update from web-platform-tests
[LayoutNG] Fix the NGExclusionSpaceInternal vectors going out of sync.
NGExclusion::operator== didn't previous compare shape_data. This turned
out to be a bad optimization. :)
Without this we'd end up in a situation where we would have:
- An exclusion vector containing an exclusion with shape data.
- Derived geometry which wasn't tracking shape data.
Bug: 963580
Change-Id: I21746f8fd081ff24658768ee6074122f2e913bd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613560
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#661191}
--
wp5At-commits: 9123f1cd8244f2290844c77025c59f27de67f795
wpt-pr: 16860
Automatic update from web-platform-tests
[LayoutNG] Fix shape exclusion tracking.
The DerivedGeometry class gets moved from exclusion-space to
exclusion-space as a fast way of determining layout opportunities (where
lines, etc get placed).
For speed we only allocate "NGShapeExclusions" if we've seen any shapes
within the formatting context.
This crash was due to an inconsistent state of the:
NGExclusionSpaceInternal::track_shape_exclusions_ flag.
"other" NGExclusionSpaceInternal
- derived_geometry_ = (non-null)
- track_shape_exclusions_ = false
- num_exclusions_ = 1u
"this" NGExclusionSpaceInternal
- derived_geometry_ = null
- track_shape_exclusions_ = true
- num_exclusions_ = 2u (2nd exclusion has shape data).
Within the NGExclusionSpaceInternal::MoveAndUpdateDerivedGeometry method
we moved the derived geometry over to the "this" exclusion space.
However we didn't also move the track_shape_exclusions_ flag as a result
we'd try to add the 2nd shape exclusion, and a NPE was hit.
Bug: 962135, 962272, 962052
Change-Id: Id095bd2924f83ba6b2dbe90446d1f4613de09933
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610021
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659678}
--
wp5At-commits: b6546f28b56bbe5122dc0e639e79057507632a86
wpt-pr: 16802
Automatic update from web-platform-tests
CSS: ellipse() has 0 or 2 radii
We were incorrectly accepting
"ellipse(10px at 20px 30px)"
as an ellipse.
Retire use count BasicShapeEllipseOneRadius 0.00002%
https://chromestatus.com/metrics/feature/timeline/popularity/2327
We were incorrectly serializing
"ellipse(10px closest-side at 20px 30px)" as
"ellipse(10px at 20px 30px)"
BUG=899150
Change-Id: I6594ff990f659be2497acb336afbb138b5d91ac8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593882
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#656441}
--
wpt-commits: a2cb833e9d8afa6ebea7dea882078277fff14d5c
wpt-pr: 16660
Automatic update from web-platform-tests
Remove inactive reviewers (#14798)
This removes reviewers who have had more than three review requests in
the past year but who haven't reviewed anything.
Adds a few extra reviewers based on discussions in the PR thread
looking for reviewers for directories that otherwise would've ended up
with none.
--
wpt-commits: a5f707c18b3d893a6e332994064911c2f11e800d
wpt-pr: 14798
Add some tests to make sure we clamp the interpolated result with
negative easing function on circle(), ellipse(), and inset().
Depends on D14654
Differential Revision: https://phabricator.services.mozilla.com/D14655
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsRename test file that conflicts with existing css test file.
--
wpt-commits: bb9c0ce15e70865a9d01a9f6dbb8568913a15d76
wpt-pr: 13313
--HG--
rename : testing/web-platform/tests/css/css-shapes/shape-outside/values/shape-outside-inset-010.html => testing/web-platform/tests/css/css-shapes/shape-outside/values/shape-outside-inset-0010.html
Automatic update from web-platform-tests[LayoutNG] Fix shape bug, when inserting a new shelf between others.
This fixes an issue, where we didn't copy across any shape exclusion
data when inserting a new shelf between two other shelves.
Bug: 635619
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ib26359ab8ac677034ec4e51f2adf1987dadbd91c
Reviewed-on: https://chromium-review.googlesource.com/1255145
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595535}
--
wpt-commits: 607280b9a23a5cec5b6185d48bcc1ea74f5815ea
wpt-pr: 13294
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-testssupport directory adjacent to parsing tests (#12541)
From https://github.com/web-platform-tests/wpt/pull/12465#issuecomment-413506239
"The CSS build system finds tests (based on <link rel=help>), moves
them to the destination direction (roughly one per spec), and then
also moves any files in an adjacent support directory. "
The support directory for the parsing test files is now adjacent to
those files.
The parsing tests previously in box-shadow-syntax-001.html
are moved into parsing/box-shadow-[in]valid.html, for consistency
with other parsing tests, and to avoid the need for an extra
copy of parsing-testcommon.js
fixes#12419
--
wpt-commits: 203c34855f6871d6e55eaf7b55b50dad563f781f
wpt-pr: 12541
--HG--
rename : testing/web-platform/tests/css/compositing/support/parsing-testcommon.js => testing/web-platform/tests/css/compositing/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-backgrounds/support/parsing-testcommon.js => testing/web-platform/tests/css/css-backgrounds/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-box/support/parsing-testcommon.js => testing/web-platform/tests/css/css-box/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-cascade/support/parsing-testcommon.js => testing/web-platform/tests/css/css-cascade/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-color/support/parsing-testcommon.js => testing/web-platform/tests/css/css-color/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-images/support/parsing-testcommon.js => testing/web-platform/tests/css/css-images/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-masking/support/parsing-testcommon.js => testing/web-platform/tests/css/css-masking/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-shapes/support/parsing-testcommon.js => testing/web-platform/tests/css/css-shapes/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-transforms/support/parsing-testcommon.js => testing/web-platform/tests/css/css-transforms/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-ui/support/parsing-testcommon.js => testing/web-platform/tests/css/css-ui/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/css-writing-modes/support/parsing-testcommon.js => testing/web-platform/tests/css/css-writing-modes/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/filter-effects/support/parsing-testcommon.js => testing/web-platform/tests/css/filter-effects/parsing/support/parsing-testcommon.js
rename : testing/web-platform/tests/css/motion/support/parsing-testcommon.js => testing/web-platform/tests/css/motion/parsing/support/parsing-testcommon.js
Automatic update from web-platform-testsRemove reviewers who have not joined the web-platform-tests org (#11888)
Part of https://github.com/web-platform-tests/wpt/issues/11293.
Reminder also in https://github.com/web-platform-tests/wpt/issues/11568.
This does not fully resolve#11293, as a few non-responders where
there would be no remaining reviewers are left, and one known to be
out-of-office. These will be handled separately to finish this.
--
wpt-commits: 8fea122cf1ed5b392c86aae5e445e7553ad83deb
wpt-pr: 11888
This reftest currently uses a container that is 1 pixel narrower than needed
to fit two blocks side-by-side. That's useful for making the first two blocks
land on separate lines, but it makes the test rely on the browser forcing the
first inline block on a line to fit even if there is no space for it (in this
case, the block that should be pushed to the right).
MozReview-Commit-ID: IxtOR2yFNn6
--HG--
extra : rebase_source : a70de7a381b4e110694314d90bd959a040014a1f
This reftest currently uses a container that is 1 pixel narrower than needed
to fit two blocks side-by-side. That's useful for making the first two blocks
land on separate lines, but it makes the test rely on the browser forcing the
first inline block on a line to fit even if there is no space for it (in this
case, the block that should be pushed to the right).
MozReview-Commit-ID: IxtOR2yFNn6
--HG--
extra : rebase_source : 03c35aba9adea56b65c8ebbc559a4d6002065c2a
Automatic update from web-platform-testsMerge pull request #10973 from csnardi/parsing-tests
Use getPropertyValue in parsing-testcommon.js
--
wpt-commits: b18d298125b77bb5da7b143500a24bbacea91746
wpt-pr: 10973
These tests use setTimeout to wait for shape-outside layout to hopefully
complete. This is non-deterministic race condition and leads to intermittent
failures. This change makes those tests instead trigger on the onload event
and removes the setTimeout infrastructure and replaces it with an assert.
Without this change, these tests have no guarantee about whether the rendering
will be complete by the time the test's JS fires.
MozReview-Commit-ID: CHrXUC3yCCT
--HG--
extra : rebase_source : b5642bf24abcbfacb7b94e95d4ca9c8d6486b98b
This adds several tests to ensure that computation of float areas for
shape-outside shapes works for elements that are offset from their containing
block.
MozReview-Commit-ID: FWUfCb9Evhl
--HG--
extra : rebase_source : bf7302ddc12631d30643d5246f90af234e07babb
This adds several tests to ensure that computation of float areas for
shape-outside shapes works for elements that are offset from their containing
block.
MozReview-Commit-ID: FWUfCb9Evhl
--HG--
extra : rebase_source : 1618d53e7be07ac460c3b7a52b75dbd4d69d8e2f
This adds several tests to ensure that computation of float areas for
shape-outside shapes works for elements that are offset from their containing
block.
MozReview-Commit-ID: FWUfCb9Evhl
--HG--
extra : rebase_source : 717ab0654ca39c6f03a602f12c28e6c4211a6179
MozReview-Commit-ID: A4UxNn4Njpi
This test applied a green color to the test area, when it should be
transparent, to allow the red to show through in case of test failure. Without
this change, this test won't catch cases where the float area is too small.
--HG--
extra : rebase_source : 8cc8c5f6dd7ddbd4eccbc48008517d0e68cff4c6
