Automatic update from web-platform-tests
Add idlharness test for element-timing (#18064)
--
wpt-commits: b6c413217de9e91590fbac9868a5720e918d4d2e
wpt-pr: 18064
Automatic update from web-platform-tests
[IntersectionObserver] Fix for rtl clipped explicit root
IntersectionGeometry::ClipToRoot uses MapToVisualRectInAncestorSpace
to map the intersection rect up to the coordinate system of the
root element's overflow rect. It then explicitly translates the
intersection rect to the root element's coordinate space and applies
the root element's clip (if any). This patch fixes the coordinate
space mapping for the case of a root element with overflow clip and a
non-zero scroll origin (e.g., direction:rtl or
flex-direction:row-reverse).
BUG=939614
R=chrishtr@chromium.org
Change-Id: I15dce9456e9791510bb331bf0cfbabd4cb04f9c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717688
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680761}
--
wpt-commits: 8aa5717cff0397f356dd494a4257fd94e60035b3
wpt-pr: 18065
Automatic update from web-platform-tests
Revert "Re-write test pointerevent_pointermove_in_pointerlock.html"
This reverts commit 9b7bafff73e59dc5d0cfcd0f499aa20be66bca54.
Reason for revert: Causing leak failures on WebKit Linux Leak bot
https://luci-milo.appspot.com/p/chromium/builders/ci/WebKit%20Linux%20Leak/2348
Original change's description:
> Re-write test pointerevent_pointermove_in_pointerlock.html
>
> The test was failing in wpt because it passing non-integer value to
> test driver. This CL changes it to use "origin" instead.
> This CL rewrites the test to makes it cleaner, instead of adding event
> listener inside event listener.
> This CL also changes the test to send the "move" events after receiving
> pointerlockchange.
>
> Bug: 986277
> Change-Id: I0f51523c3c90791339877b2e51afa8e9a4cc9d4d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717195
> Reviewed-by: Lan Wei <lanwei@chromium.org>
> Commit-Queue: Ella Ge <eirage@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#680563}
TBR=lanwei@chromium.org,eirage@chromium.org
Change-Id: Ia53d1066363ceaf804f61ada369a4126c859f875
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 986277
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716038
Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680743}
--
wpt-commits: a285d1bbbc1921bc976aab1af4238a8e304ecbab
wpt-pr: 18066
Automatic update from web-platform-tests
Organize webxr internal and external tests
Moves all remaining internal webxr tests that can be made external to
external/wpt/webxr. For tests that were not moved a comment was added
explaining what is keeping the test internal. And a README was added to
also call out these requirements.
Most tests were ported as-is (with the exception of changing the scripts
that they include), but substantial updates were required to a couple
in order to better align with the spec:
xrWebGLLayer_constructor was modified to be more similar to the deleted
xrWebGLLayer_incompatible_device, since that also tested the constructor
just with a gl context that had not yet been made xrCompatible. This
test is now more explicit about what it is doing.
render_state_vertical_fov_inline was cloned to an external version that
tests that setting a value below the min or above the max stays inside
the min and max range, but does not test the specific expected value,
since that is not required by the spec. Chrome is keeping an internal
version of that test with it's chosen min/max.
Bug: 863557
Change-Id: I81d6d4bbbdf7e60e8576eb6a8dfbd422aa95013e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715732
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680665}
--
wpt-commits: 453453af2e854b13228cab2da314cc2a4d1ffc86
wpt-pr: 18026
Automatic update from web-platform-tests
Indexed DB: Migrate "Structured Clone" test to WPT
Pros:
* Switch from js-test to testharness
* Cover a bunch more ECMAScript and Platform types
* Runs in Window and Worker contexts
* Decreases coverage for FileList interface
* Somewhat redundant with WPT's html/infrastructure/safe-passing-of-structured-data
Cons:
Change-Id: If80ce64a88caa9b3d0e409bdac5712ca795a1785
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1709787
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680653}
--
wpt-commits: d0691cc870b3ea1f5dc516f53817d2c3377aab9a
wpt-pr: 17951
Automatic update from web-platform-tests
[css-properties-values-api] Reify specified values as CSSUnparsedValue
According to a recent spec change, the syntax of a registered custom
property must be ignored until computed-value time. This means that
we can unfortunately not reify specified values according to the
syntax; instead all custom properties reify as CSSUnparsedValue,
regardless of their registration status.
This means that we can remove large parts of the Typed OM code which
deals with PropertyRegistation for specified values and matching of
incoming CSSStyleValues against registered syntax.
The typedom.html test was also mostly re-written, as most of the things
it tested are now not relevant anymore, or at least no longer as
interesting as before. (The new reworked test basically verifies that
registered custom properties behave as unregistered for
attributeStyleMap and styleMap. For computedStyleMap, we should of
course still reify according to the syntax).
Bug: 641877
Change-Id: I4da7c25b8f066dd01388b6229bebe181513e9fd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713557
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680595}
--
wpt-commits: 8c0c1caee779ea4ad0dee2484be0234d14f54b7b
wpt-pr: 18032
Automatic update from web-platform-tests
Re-write test pointerevent_pointermove_in_pointerlock.html
The test was failing in wpt because it passing non-integer value to
test driver. This CL changes it to use "origin" instead.
This CL rewrites the test to makes it cleaner, instead of adding event
listener inside event listener.
This CL also changes the test to send the "move" events after receiving
pointerlockchange.
Bug: 986277
Change-Id: I0f51523c3c90791339877b2e51afa8e9a4cc9d4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717195
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680563}
--
wpt-commits: 69f536cd9cc57f20a6d27acb70b7b05c6434b24d
wpt-pr: 18053
Automatic update from web-platform-tests
[wptrunner] Expose headless flag for expected meta data.
Differential Revision: https://phabricator.services.mozilla.com/D36723
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1493907
gecko-commit: 0609705a34727f7049ce2e97f214823031b5f703
gecko-integration-branch: central
gecko-reviewers: webdriver-reviewers, ato
--
[wdspec] Mark remaining failing tests as expected fail for headless mode.
Differential Revision: https://phabricator.services.mozilla.com/D36725
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1493907
gecko-commit: d62f57d8e0b72ba75be5b50bb02d042ec2ace36c
gecko-integration-branch: central
gecko-reviewers: webdriver-reviewers, ato
--
Default to False if headless is not present in extras
--
wpt-commits: b8f571905fe06bf3a7d2c3d8ef0ba90176e9aff6, 61fcd02cdb3ee095bc12828cebcf9b0c00080f0b, 740f7dfc63ed0d1ae68f28cb1097bd927c5a24bf
wpt-pr: 17724
Automatic update from web-platform-tests
MathML: Add tests for padding / margin / border-width (#18046)
These are very basic tests to check support for
https://github.com/mathml-refresh/mathml/issues/14
Put in a dedicated folder since it's likely that we need a more lot tests.
--
wpt-commits: b9480320a5775a8cbb28725246070273c20cdf83
wpt-pr: 18046
Automatic update from web-platform-tests
[wpt PR 16993] - webrtc wpt: validate connectionstate goes to failed with wrong fingerprints, a=testonly
Automatic update from web-platform-tests
webrtc wpt: validate connectionstate goes to failed with wrong fingerprints
Modifies the SDP to pass an different fingerprint from the one that is used which
results in a DTLS failure/alert as the fingerprint does not match the certificate.
Bug: none
Change-Id: Ice8adf70f57e7da02fc014bb43b0c78841bfd9aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627362
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#663037}
--
wp5At-commits: 80853e045ef85c804e639570690481db6e15a53e
wpt-pr: 16993
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1554087
gecko-commit: f5fd810645175d8996685aebb59fd0417df92dfb
gecko-integration-branch: central
gecko-reviewers: testonly
--
wpt-commits: a652b55a74698ba3b5731c6b10194f0f090b71bc
wpt-pr: 17466
Automatic update from web-platform-tests
[docs] Simplify list
--
[docs] Correct description of file formats
Previously, the description of test file formats was incomplete and
somewhat confusingly-worded. Expand the explanation to fully describe
the accepted formats, and include additional advice for how to learn
more in context.
--
[docs] Remove duplicated section
This section is also included in the "General Guidelines" document which
describes expecations for all tests, including "rendering tests."
--
[docs] Remove presumptuous commentary
The word "obviously" may discourage readers for whom the following
statement was not obvious. Remove it and simplify the sentence
structure.
--
[docs] Hyphenate related words
--
wpt-commits: 1943a7a4921150ed362482b839a9fbf9635a0d92, ffc09bc63f93f3d2e153c3f259e48a95616973fb, e9883fb07146de6f4eacd0ced0463c7ed079f5f3, bff26a740d4bec5af9a55f5be94b9d7d63dd80db, e31ca03d7851ecced4ee9b212780a82d30c544fe
wpt-pr: 17751
Automatic update from web-platform-tests
[css-typed-om] Don't crash when setting CSSVariableReferenceValue.
When creating a CSSVariableReferenceValue with a reference to a variable
which actually exists, we crash because CSSVariableReferenceValue objects
created through Typed OM don't have a CSSParserContext. This was missed
by our existing test suite, because we only covered a similar case where
the referenced variable *didn't* exist, avoiding the broken code path.
For now, fixed by using StrictCSSParserContext.
Bug: 986710, 985028
Change-Id: If51e34a77e5433849e0602f297909027fc743798
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713627
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680390}
--
wpt-commits: 06df984b711fd57d11650a6dc40930c6e19a1ac1
wpt-pr: 17994
Automatic update from web-platform-tests
[css-properties-values-api] Accept any value through setProperty.
According to a recent spec change, the syntax of a registered custom
property must be ignored until computed-value time. This means that
setProperty may not inspect the PropertyRegistry and reject values
based on that.
This CL also removes the PropertyRegistry parameter in many places, to
avoid incorrectly using it in the future.
Bug: 641877
Change-Id: I99c58775e800500862378420118d81fe3186e739
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1714590
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#680388}
--
wpt-commits: 501317b2dee0c1be2dce818739f53a547a8a4398
wpt-pr: 18029
Automatic update from web-platform-tests
Fix metadata expectations for actionsWithKeyPressed.html
This always fails on Mac at least in Chrome and Firefox; probably the test is just wrong on that platform.
Ensure the metadata is correct to unblock other PRs.
--
wpt-commits: 1fad9be19ce2e1aead60e62180167e43930087bd
wpt-pr: 18031
Since we modified the Editor to be accessible, we got
the green light to remove the old JsTerm code.
This means we can remove the preference for the codeMirror
input, and clean the WebConsole react app a bit.
This also mean we can avoid running a lot of our tests
twice.
Finally, some test helpers had to take argument with
specific shape to work against old jsterm (e.g. checkInputCompletionValue),
that we can now remove to make tests easier to read.
Differential Revision: https://phabricator.services.mozilla.com/D40172
--HG--
extra : moz-landing-system : lando
All of these tests current fail due to fuzzy upscaling/downscaling behavior,
which the tests aim to work around using `image-rendering: pixelated`, but we
don't yet support that feature. I've added the bug link for that feature to
these .ini files, so that we'll get a clue to remove these annotations once we
fix that bug and implement that feature.
Differential Revision: https://phabricator.services.mozilla.com/D40146
--HG--
extra : moz-landing-system : lando
This annotation matches the one in
layout/reftests/css-invalid/select/reftest.list for
select-disabled-fieldset-1.html (which should really produce the same
rendering, and have the same reference).
This is a one-pixel fuzz on the fieldset border near the bottom right corner.
It's unclear which patch of this pushlog, if any, caused this:
https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=4a49d88894d8d88f87760ac59ae35b2158fab7b2
Probably bug 1404868, which added reftests and tickled something. But it seems
this is not really that patches' fault, so to avoid speculatively backing it
out, with the chance of it not being the offender, let's mark it as fuzzy for
now.
I kept the exact same annotation as the other test, since this goes directly to
central, so it's less risky.
We could try to make it fuzzy-if(Android,9-9,1-1), maybe, though given it seems
to be affected to changes to adjacent reftests that may be unwise.
Skip whitespace upfront rather than on each individual branch. The only
difference in behavior is that we would've consumed some extra whitespace in the
error case, but I don't think that matters at all.
We were consuming some extra whitespace as well after the close path command for
example, which wasn't parsing anything.
Depends on D40538
Differential Revision: https://phabricator.services.mozilla.com/D40539
--HG--
extra : moz-landing-system : lando
None cannot be returned, since we just called peek() and it returned something.
Differential Revision: https://phabricator.services.mozilla.com/D40538
--HG--
extra : moz-landing-system : lando
I made changes to the `LOCALIZATION NOTE` in the `inspector.properties` file and updated `DISPLAY_TYPES` in the `element-editor.js` file for `flex`, `grid`, `inline-flex` and `inline-grid`.
Differential Revision: https://phabricator.services.mozilla.com/D40537
--HG--
extra : moz-landing-system : lando
The connect function was very hard to follow, with other methods
responsible to resolve or reject the connection Promise.
We modify this to only deal with the connection Promise inside
the connect function so it's easier to follow.
The connection timeout was handled in a similar fashion, with
the callback to a setTimeout responsible to reject the connection
promise.
We modify this behavior in favor of a Promise.race which brings
us the same benefit while being easier to understand.
Differential Revision: https://phabricator.services.mozilla.com/D39471
--HG--
extra : moz-landing-system : lando
