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
Automatic update from web-platform-tests
Add support for fuzzy matching in reftests (#12187)
This allows fuzzy matching in reftests in which a comparison can
succeed if the images are different within a specified tolerance. It
is useful in the case of antialiasing, and in other scenarios where
it's not possible to make an exact match in all cases.
Differences between tests are characterised by two values:
* The maximum difference for any pixel on any color channel (in the
range 0 to 255)
* The maximum total number of differing pixels
The fuzziness can be supplied in two places, according to whether it's
a property of the test or of the implementation:
* In the reftest itself, using a <meta name=fuzzy> tag
* In the expectation metadata file using a fuzzy: key that takes a
list
The general format of the fuzziness specifier is
range = [name "="] [digits, "-"], digits
fuzziness = [ url, "-" ], range, ";", range
name = "maxDifference" | "totalPixels"
The first range represents the maximum difference of any channel per
pixel and the second represents the total number of pixel
differences. So for example a specifier could be:
* "maxDifference=10;totalPixels=300" - meaning a difference of exactly
10 per color channel and exactly 300 pixels different in total (all
ranges are inclusive).
* "5-10;200-300" - meaning a maximum difference of between 5 and 10
per color channel and between 200 and 300 pixels differing in total
The definition of url is a little different between the meta element
and the expecation metadata. In the first case the url is resolved
against the current file, and applies to any reference in the current
file with that name. So for example
<meta name="fuzzy" content="option-1-ref.html:5;200">
would allow a fuzziness of up to 5 on a specific channel and up to 200
opixels different for comparisons involving the file containing the
meta element and option-1-ref.html.
In the case of expectation metadata, the metadata is always associated
with the root test, so urls are always resolved relative to that. In
the case as above where only a single URL is supplied, any reference
document with that URL will have the fuzziness applied for whatever
comparisons it's involved in e.g.
[test1.html]
fuzzy: option-1-ref.html:5;200
would apply the fuziness to any comparison involving option-1-ref.html
whilst running the set of reftests rooted on test1.html. To specify an
exact comparison for the fuzziness, one can also supply a full
reference pair e.g.
[test1.html]
fuzzy: subtest.html==option-1-ref.html:5;200
in which case the fuzziness would only apply to "match" comparison
involving subtest.html on the lhs and option-1-ref.html on the
rhs (both resolved relative to test1.html).
--
wpt-commits: 1f570a686843ca10f151a79956ee16110f4a4d42
wpt-pr: 12187
Automatic update from web-platform-tests
[docs] Correct page formatting (#15532)
Insert the YAML frontmatter which distinguishes page content and causes
Jekyll to create an HTML document during the website rendering process.
--
wpt-commits: 70df598b894bfa4a7122720608a3110cb25ceb42
wpt-pr: 15532
Automatic update from web-platform-tests
[docs] Reorganize information on running the tests
Previously, information was organized as follows:
- Section: Introduction
- Page: Introduction
- Introductory material
- Instructions for running the tests manually
- Abbreviated instructions for `wpt run`
- Section: Running the Tests
- Page: Running the Tests
- Instructions for `wpt run`
- Instructions for the web runner
- Notes on writing a custom runner
Dispersing the information about "test running" across multiple sections
tended to dilute the meaning of each section. It also made the
introduction lengthier and possibly more intimidating (especially for
readers who have no intention of running the tests manually).
Restructure the information as follows:
- Section: Introduction
- Page: Introduction
- Introductory material
- Section: Running the Tests
- Page: Running the Tests
- Instructions for running the tests manually
- Reference to "Running the Tests in Automation"
- Page: Running the Tests in Automation
- Instructions for `wpt run`
- Instructions for the web runner
- Notes on writing a custom runner
--
wpt-commits: c271bdc85efc27839b01ec5aecf4f3a22084d820
wpt-pr: 13125
Automatic update from web-platform-tests
Change reftest size to 800x600 everywhere (#12695)
With Firefox, with the internal reftest runner (used by default), this
doesn't actually change the reftest size in Firefox versions prior to
66 (currently on the beta channel); to get the correct behaviour with
older versions of Firefox, you must pass `--reftest-external` to use
the external reftest runner.
--
wpt-commits: d5f07ed3b5186e553940a3d5c547067850a4e3f0
wpt-pr: 12695
Automatic update from web-platform-tests
[testdriver] Enable manual interaction (#11173)
The testdriver.js utility allows tests which require user input to be
fully automated. It requires that the browser be under the control of a
WebDriver server in order to do this.
In test maintenance contexts, this requirement can slow development
because a new browsing session must be created for each trial, and
debugging tools such as the developer's console cannot be used.
This requirement also limits the tests' value to a larger audience when
published online. Visitors to sites like w3c-test.org are interested in
observing test results experimentally, but although they may be capable
of providing the expected input, the hard requirement on WebDriver will
cause tests to fail unconditionally.
Extend the framework to accept traditional human input if the test is
being run without the WebDriver technology. This allows test authors to
debug tests and other interested parties to verify results in browsers
of their choosing. It does not interfere with fully-automated test
execution.
--
wpt-commits: bfd9504d321d35ebfbbe56ab6c7f5c0642495719
wpt-pr: 11173
Automatic update from web-platform-tests
[docs] Correct page formatting (#15532)
Insert the YAML frontmatter which distinguishes page content and causes
Jekyll to create an HTML document during the website rendering process.
--
wpt-commits: 70df598b894bfa4a7122720608a3110cb25ceb42
wpt-pr: 15532
Automatic update from web-platform-tests
[docs] Reorganize information on running the tests
Previously, information was organized as follows:
- Section: Introduction
- Page: Introduction
- Introductory material
- Instructions for running the tests manually
- Abbreviated instructions for `wpt run`
- Section: Running the Tests
- Page: Running the Tests
- Instructions for `wpt run`
- Instructions for the web runner
- Notes on writing a custom runner
Dispersing the information about "test running" across multiple sections
tended to dilute the meaning of each section. It also made the
introduction lengthier and possibly more intimidating (especially for
readers who have no intention of running the tests manually).
Restructure the information as follows:
- Section: Introduction
- Page: Introduction
- Introductory material
- Section: Running the Tests
- Page: Running the Tests
- Instructions for running the tests manually
- Reference to "Running the Tests in Automation"
- Page: Running the Tests in Automation
- Instructions for `wpt run`
- Instructions for the web runner
- Notes on writing a custom runner
--
wpt-commits: c271bdc85efc27839b01ec5aecf4f3a22084d820
wpt-pr: 13125
Automatic update from web-platform-tests
Change reftest size to 800x600 everywhere (#12695)
With Firefox, with the internal reftest runner (used by default), this
doesn't actually change the reftest size in Firefox versions prior to
66 (currently on the beta channel); to get the correct behaviour with
older versions of Firefox, you must pass `--reftest-external` to use
the external reftest runner.
--
wpt-commits: d5f07ed3b5186e553940a3d5c547067850a4e3f0
wpt-pr: 12695
Automatic update from web-platform-tests
[testdriver] Enable manual interaction (#11173)
The testdriver.js utility allows tests which require user input to be
fully automated. It requires that the browser be under the control of a
WebDriver server in order to do this.
In test maintenance contexts, this requirement can slow development
because a new browsing session must be created for each trial, and
debugging tools such as the developer's console cannot be used.
This requirement also limits the tests' value to a larger audience when
published online. Visitors to sites like w3c-test.org are interested in
observing test results experimentally, but although they may be capable
of providing the expected input, the hard requirement on WebDriver will
cause tests to fail unconditionally.
Extend the framework to accept traditional human input if the test is
being run without the WebDriver technology. This allows test authors to
debug tests and other interested parties to verify results in browsers
of their choosing. It does not interfere with fully-automated test
execution.
--
wpt-commits: bfd9504d321d35ebfbbe56ab6c7f5c0642495719
wpt-pr: 11173
Automatic update from web-platform-tests
Clarify that object arg to assert_throws is for non-DOMExceptions
Previous text made it seem like passing any object with the correct "name" property would be fine, but in reality, if you're specifically expecting a DOMException, you should be passing a string. (per @Ms2ger feedback)
Preserved the original wording as much as possible otherwise.
(Probably `assert_throws` itself should check the error type if called with an object, and verify that it's *not* a DOMException. But that's a separate cleanup project.)
--
wpt-commits: 59ea76c698b416231e7dcdb877a6265ba82b49f8
wpt-pr: 15116
Automatic update from web-platform-tests
Change all references of reftest size to be 600x600
--
Add a infra test for reftest size
--
Fix#12578: make {Selenium,WebDriver} use the right size for reftests
Also drop some dead code reading reftest.js.
--
Disable the automation extension for Chrome unconditionally
--
wpt-commits: c5f9c98347a577a328e282e6f64221b4bbd24562, 8a58198bb9e45c83f51b0e39edf44c796fc126ba, cd697ab2768b0953eff0a29d10f4a1a9721ed8e3, 7f72bad3bfb5f1ea5ee765550e1767cf4a63a704
wpt-pr: 14922
Automatic update from web-platform-tests
Stop explicitly listing hosts in chrome_android.md
Point to `wpt make-hosts-file` instead.
--
wpt-commits: d57cb918ef2b0fbc79c39cb48f6870d02040d4d3
wpt-pr: 14806
Automatic update from web-platform-tests
Add actions builder API documentation
Add actions builder API documentation plus some examples
--
Remove trailing space and add a "the"
--
wpt-commits: 07e35f356cc4a6b2a27a0d9f2a14968d5ee7330a, d67fec6063da225ec5da00db820a401783922264
wpt-pr: 14287
Automatic update from web-platform-testsDocument the source email for assignment (#14214)
--
wpt-commits: ad865c2f6bd3ce9ab1333eb78df445cd4c805f36
wpt-pr: 14214
Automatic update from web-platform-testsDocument the source email for assignment (#14214)
--
wpt-commits: ad865c2f6bd3ce9ab1333eb78df445cd4c805f36
wpt-pr: 14214
Automatic update from web-platform-testsAdds Self Describibing section to rendering docs
--
made the requested changes
--
removing extra line
--
removing one more extra line
--
making rest words non capitalize
--
wpt-commits: 79a7cb3e24c189a43a3a890fc7796132bbd4fd5a, d08838132faa67d3240eb4048c5d8387a0b927a3, ef5f7b1be322d8ed416c44f333fcec1fa255032c, 24123f32aa98effb22ce755aacc8765c0da4a2f8, 0cd1d2859d28fd15f5483c298e7d54b34b5665f0
wpt-pr: 13809
Automatic update from web-platform-testsFix the documentation of `action_sequence` somewhat (#13680)
--
wpt-commits: f709c0bcdff406cd539a02cf8c57122f025a16bb
wpt-pr: 13680
Automatic update from web-platform-testsMove and fix the action_sequence documentation (#13648)
--
wpt-commits: 2b758296541cf4f2209b8c2352cf6c7890c97be3
wpt-pr: 13648
Automatic update from web-platform-testsAdd a `.optional.` file name flag for optional behavior (#13586)
--
wpt-commits: 80dce24781817a9091b3ed5094dbd2b58386d152
wpt-pr: 13586
Automatic update from web-platform-testsUpdate setup instructions for Safari to use `no_proxy='*'` (#13569)
--
wpt-commits: ad38861e9b15056b8bf2c58b62508d02b8f9c78a
wpt-pr: 13569
Automatic update from web-platform-testsSupport `./wpt run --channel=preview safari` (#13460)
This mostly to avoid the lengthy argument currently required:
`--webdriver-binary "/Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver"`
Using `--browser-channel=preview` and the product `safari_webdriver`
also works.
--
wpt-commits: 9f2daa2a5d08d0d44f680501af2b62292f6264f0
wpt-pr: 13460
Automatic update from web-platform-testsAdd action sequence injection in test_driver
Following web driver spec for pointer action
sequence and key actions this change adds this
API to the test_driver interface.
Use action_sequence instead of pointer_action_sequence
--
[testdriver] Support sending actions sequences over WebDriver
--
[testdriver] Add a builder object for constructing actions
Action sequences are not really sensible to construct by hand, so this
adds a builder object for constructing sequences of actions. To use it
the following script mut be included after testdriver.js:
<script src="/resources/testdriver-actions.js"></script>
Then actions sequences can be constructed like
// Drag the mouse from 0,0 to 100,100 with ctrl held down
test_driver.Actions()
.pointerMove(0, 0, origin="viewport")
.keyDown("\uE009")
.pointerDown()
.pointerMove(100, 100, origin="viewport")
.pointerUp()
.keyUp()
.send();
--
Fix error handling for testdriver tests.
Otherwise a protocol error leads to FAIL not ERROR.
--
Add element_by_selector to SelectorProtocolPart
--
wpt-commits: ceadf71f63047e88dddd9308fd9f06db24ecfb29, f1db6b22cf40d6b56665225dfd4f83bbddd76686, 01dfc0f42edacd529749fcf543e16431ba7a9490, 723dcaffe979639976dee773c09eb24694625c23, a9504407fb46702dbb2bba7df9d349d8eba7ce55
wpt-pr: 12726
Automatic update from web-platform-tests[docs] Add information on project administration
Document the various secrets and accounts necessary to administer
web-platform-tests and its related project.
--
fixup! [docs] Add information on project administration
--
fixup! [docs] Add information on project administration
--
fixup! [docs] Add information on project administration
--
fixup! [docs] Add information on project administration
--
fixup! [docs] Add information on project administration
--
Fix typo
--
Add information about wpt-pr-bot GH account
--
wpt-commits: 8361f5c2dfd0fa59388d72b7a7d6ad11617a891d, cad6d894c152066b8ae2fe1663ba34cd0805d424, d5049bca940cf3c5a5e61aa6432f27cc9dd5c9f1, 53b410f29d87c453f758c7513ec15bfeff6dbc6c, 9d9433d92a7150bc9bc5bd0791ccec0f0ee1af48, 1d2bcbaa86ec8320097377c56a10d99bf81627ff, 4eb0a434accb3a86b7dfd044c58f3562f6bad66b, d242e14f16d37a43155103e02a00de79247a678d
wpt-pr: 10832
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-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[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
Automatic update from web-platform-testsFix 'link' syntax in MISSING-LINK explainer (#12987)
The correct syntax for the 'link' element uses 'href', not 'src'.
--
wpt-commits: 92d2e6216ed2788c286510a0b58d9d8337d45111
wpt-pr: 12987
Automatic update from web-platform-tests[testharness.js] Reject non-thenable values (#12898)
Previously, any test defined via the `promise_test` API would fail
immediately if its body returned the value `undefined`. The test would
*not* fail if it returned any other value. Because the motivation for
using `promise_test` is to track resolution with a "thenable" value
(i.e. an object with a "then" method), this was overly permissive and
allowed contributors to write tests which spuriously passed [1].
Update testharness.js to enforce more stringent criteria on the value
return by `promise_test` bodies: that it is a "thenable" value. This
change is incompatible with an exiting functional test, but it does not
effect any tests in WPT (as verified by a survey using both the Chrome
and Firefox browsers). Update the functional test accordingly.
[1] cca6b6845678d9b5f792b886f3f7045d1d2cf0a7
--
wpt-commits: 86579034357501943927f3dc4abf75d76c477383
wpt-pr: 12898
Automatic update from web-platform-testsImprove the formatting of testdriver documentation
In https://web-platform-tests.org/writing-tests/testdriver.html it is currently
hard to tell where the different sections begin and end because the formatting
of headings looks just like a line of code.
--
wpt-commits: d33f14555351b58c944eb50b9c46d7d9a930773a
wpt-pr: 12883
