5812789 | Ms2ger | 02 March 2017, 12:04:34 UTC | fixup! Use the print function in some scripts. | 02 March 2017, 12:04:34 UTC |
9e2174d | Ms2ger | 02 March 2017, 12:01:45 UTC | try | 02 March 2017, 12:01:45 UTC |
f907499 | Ms2ger | 02 March 2017, 11:53:04 UTC | Run the lint on python 3. | 02 March 2017, 11:53:04 UTC |
c638b39 | Ms2ger | 02 March 2017, 11:52:04 UTC | Use Python3-compatible except syntax. | 02 March 2017, 11:52:04 UTC |
c82d4ec | Ms2ger | 02 March 2017, 11:51:35 UTC | Use the print function in some scripts. | 02 March 2017, 11:51:35 UTC |
1856128 | shans | 01 March 2017, 09:06:14 UTC | CSSMatrixComponent mutable matrix test. (#4715) | 01 March 2017, 09:06:14 UTC |
62829b4 | shans | 01 March 2017, 09:03:26 UTC | [css-typed-om] Test that styleMaps have an update function. (#4723) | 01 March 2017, 09:03:26 UTC |
8776ab5 | shans | 01 March 2017, 08:59:26 UTC | Test that inherit is accepted in element styleMaps. (#4718) | 01 March 2017, 08:59:26 UTC |
f2bec30 | Tomoyuki Shimizu | 01 March 2017, 07:49:02 UTC | [presentation-api] Update IDL tests for a receiving user agent (#5029) Updates the IDL tests that check a receiving user agent. Note that, while the receiving user agent is the user agent under test, the test actually needs to be run from a controlling user agent, first because that is the only way to create a receiving context, and second for the test to integrate better with the test runner that will run on the controlling side. The receiving user agent will report the IDL tests results to a stash on the server. The controlling user agent will retrieve these results, render them in the controlling page, and pass them on to the test runner if it exists. | 01 March 2017, 07:49:02 UTC |
9490a0f | jugglinmike | 28 February 2017, 18:28:24 UTC | [editing] Correct duplicated test names (#4759) * [editing] Remove duplicated tests * [editing] Promote unique test name generation Some tests may specify a command sequence that includes multiple invocations of the same command. In particular, this includes non-idempotent commands such as "underline." The following test case from `multiline.js` demonstrates such a usage: ["foo[]bar", [["createlink","http://www.google.com/"],["underline",""],["underline",""],["inserttext","a"]], "foo<a href=\"http://www.google.com/\">a[]</a>bar", [true,true,true,true], {"createlink":[false,false,"",false,false,""],"underline":[false,false,"",false,true,""],"inserttext":[false,false,"",false,false,""]}], Because test names should be unique, this means that the command's name alone is not sufficient input to construct an appropriate name for the test asserting the command's effect. Extend the logic for generating test names to include the command's position in the sequence, ensuring that multiple invocations of the same command produce uniquely-named tests. * fixup! [editing] Promote unique test name generation * fixup! [editing] Promote unique test name generation * fixup! [editing] Promote unique test name generation | 28 February 2017, 18:28:24 UTC |
00b21d4 | James Graham | 28 February 2017, 15:48:27 UTC | Update to latest wpt-tools | 28 February 2017, 15:48:57 UTC |
7134e5a | James Graham | 28 February 2017, 14:25:01 UTC | Update to latest wpt-tools | 28 February 2017, 14:25:01 UTC |
82dd70b | Bob Holt | 23 February 2017, 15:25:19 UTC | show list of errors on inconsistent tests | 28 February 2017, 10:41:18 UTC |
29fec53 | Chromium WPT Sync | 28 February 2017, 05:10:09 UTC | Merge pull request #5030 from w3c/chromium-export-try selection: Update addRange-nn.html for 20170227 draft. | 28 February 2017, 05:10:09 UTC |
8a1fddc | tkent | 28 February 2017, 04:50:13 UTC | selection: Update addRange-nn.html for 20170227 draft. addRange() behavior was updated so that it does nothing if rangeCount > 0. https://www.w3.org/TR/2017/WD-selection-api-20170227/#dom-selection-addrange BUG=683066 Review-Url: https://codereview.chromium.org/2719813004 Cr-Commit-Position: refs/heads/master@{#453498} | 28 February 2017, 04:50:13 UTC |
4e8d373 | Victor Costan | 28 February 2017, 04:16:36 UTC | Remove dropzone from DOM tests. (#5018) The dropzone attribute is being removed from the HTML specification, per https://github.com/whatwg/html/issues/2331. This is part of a series of PRs that aim to remove the attribute from web-platform-tests. | 28 February 2017, 04:16:36 UTC |
b79bbcc | Chromium WPT Sync | 27 February 2017, 22:20:09 UTC | Merge pull request #5028 from w3c/chromium-export-try Turn on the flag for 'allow-top-navigation-by-user-activation'. | 27 February 2017, 22:20:09 UTC |
adf2ea3 | binlu | 27 February 2017, 22:10:13 UTC | Turn on the flag for 'allow-top-navigation-by-user-activation'. Change the feature of TopNavByUserActivationInSandbox from "experimental" to "stable". Refine the words in the WPT test for 'allow-top-navigation-by-user-activation'. Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/El0ueyoNgRE BUG=662506 Review-Url: https://codereview.chromium.org/2713283002 Cr-Commit-Position: refs/heads/master@{#453327} | 27 February 2017, 22:10:13 UTC |
c442b2e | Chromium WPT Sync | 27 February 2017, 22:00:10 UTC | Merge pull request #5027 from w3c/chromium-export-try [InputEvent] Change |InputEventInit::sequence<Range> ranges| to |sequence<StaticRange> targetRanges| | 27 February 2017, 22:00:10 UTC |
fe99f88 | chongz | 27 February 2017, 21:40:14 UTC | [InputEvent] Change |InputEventInit::sequence<Range> ranges| to |sequence<StaticRange> targetRanges| See spec https://w3c.github.io/input-events/#h-interface-inputevent BUG=692700 Review-Url: https://codereview.chromium.org/2709883004 Cr-Commit-Position: refs/heads/master@{#453306} | 27 February 2017, 21:40:14 UTC |
8dcf424 | Chromium WPT Sync | 27 February 2017, 21:30:10 UTC | Merge pull request #5026 from w3c/chromium-export-try Send pointer events regardless of it being a disabled form control. | 27 February 2017, 21:30:10 UTC |
df6944f | dtapuska | 27 February 2017, 21:12:47 UTC | Send pointer events regardless of it being a disabled form control. Seems pointer events carried over a model from mouse events that it shouldn't have. Always dispatch pointer events to disabled form controls. BUG=695979 Review-Url: https://codereview.chromium.org/2716063002 Cr-Commit-Position: refs/heads/master@{#453305} | 27 February 2017, 21:12:47 UTC |
217dcf1 | Adam Rice | 27 February 2017, 19:51:55 UTC | Rename ReadableStreamReader to ReadableStreamDefaultReader Use the name "ReadableStreamDefaultReader" for the default reader in tests to match the standard. Also change the test filenames from readable-stream-reader.* to default-reader.*. | 27 February 2017, 19:51:55 UTC |
ebff944 | Andreas Tolfsen | 27 February 2017, 17:36:38 UTC | Merge pull request #5024 from w3c/actions_timeout Add a long timeout to the wdspec actions test. | 27 February 2017, 17:36:38 UTC |
4dd5810 | Andreas Tolfsen | 27 February 2017, 17:35:31 UTC | Merge pull request #5023 from w3c/webdriver_url Add url fixture and update actions tests to use it | 27 February 2017, 17:35:31 UTC |
0c71d24 | Andreas Tolfsen | 27 February 2017, 17:33:58 UTC | Merge pull request #5022 from w3c/wdspec_fixup WebDriver test fixes to work with current wdclient | 27 February 2017, 17:33:58 UTC |
7a70791 | Jake Archibald | 27 February 2017, 10:32:58 UTC | Marking tests as HTTPS. I wasn’t aware of the convention when I wrote these. | 27 February 2017, 16:45:39 UTC |
f57d056 | James Graham | 27 February 2017, 16:42:40 UTC | Add a long timeout to the wdspec actions test. | 27 February 2017, 16:43:42 UTC |
d27d55e | James Graham | 27 February 2017, 16:31:31 UTC | Webdriver test fixes to work with current wdclient | 27 February 2017, 16:38:10 UTC |
4d4c0ca | James Graham | 27 February 2017, 16:24:42 UTC | Add url() fixture and update actions tests to use it. | 27 February 2017, 16:36:20 UTC |
64d2026 | Tomoyuki Shimizu | 27 February 2017, 08:29:39 UTC | [Presentation API] Controller tests on communication channel (#4950) New tests to check the communication channel, from a controlling page perspective. Tests check the "send()" method and the "message" event handler with different types of data. The Presentation API communication channel is the purpose of the tests. As such the tests cannot assume that the communication channel behaves correctly, and control messages between the controlling page and the receiving page rather go through a stash on the wptserve server. | 27 February 2017, 08:29:39 UTC |
a8461e4 | Marcos Cáceres | 27 February 2017, 02:06:04 UTC | Add marcoscaceres as owner | 27 February 2017, 02:27:31 UTC |
3c42833 | Domenic Denicola | 26 February 2017, 20:07:56 UTC | Update select event tests for spec change and completeness (#4799) This updates the tests for the select event on inputs and textareas in a few ways: - It adds tests that they do not fire for a non-changing selection, per the spec change in https://github.com/whatwg/html/pull/2352. - It tests them more exhaustively, for all selection APIs including the setters - It consolidates them inside the single select-event.html file instead of having some in the files for their respective methods. | 26 February 2017, 20:07:56 UTC |
4d1e656 | Brandon Maslen | 25 February 2017, 07:37:52 UTC | Fetch keepalive quota tests Initial set of quota tests for keepalive fetch requests. See https://github.com/whatwg/fetch/pull/419 for details. | 25 February 2017, 07:37:52 UTC |
0be3f21 | Chromium WPT Sync | 25 February 2017, 01:20:11 UTC | Merge pull request #5016 from w3c/chromium-export-try ServiceWorker: Change base URL for parsing script URL and scope URL | 25 February 2017, 01:20:11 UTC |
c3e1d2d | jungkee.song | 25 February 2017, 01:10:13 UTC | ServiceWorker: Change base URL for parsing script URL and scope URL According to the spec change, this changes to use the relevant settings object instead of the entry settings object to parse the script URL and the scope URL given to ServiceWorkerContainer.register() and ServiceWorkerContainer.getRegistration(). Before this CL, register() and getRegistration() used entered execution context to parse the URLs. After this CL, the methods use the execution context retrieved from ScriptState::getExecutionContext(). WPT: external/wpt/service-workers/service-worker/multi-globals/url-parsing.https.html Spec issue: https://github.com/w3c/ServiceWorker/issues/922 Spec change: https://github.com/w3c/ServiceWorker/commit/ec1aac220646a5ea15583e22da1373581a8f2f23 BUG=691008 Review-Url: https://codereview.chromium.org/2691903005 Cr-Commit-Position: refs/heads/master@{#453033} | 25 February 2017, 01:10:13 UTC |
2df2dc1 | Marcos Cáceres | 24 February 2017, 23:12:31 UTC | Add @marcoscaceres as owner for PaymentRequest | 24 February 2017, 23:12:31 UTC |
abd9093 | Chromium WPT Sync | 24 February 2017, 23:00:11 UTC | Merge pull request #5013 from w3c/chromium-export-try Selection API: add removeRange(). | 24 February 2017, 23:00:11 UTC |
55c8239 | tkent | 24 February 2017, 22:50:13 UTC | Selection API: add removeRange(). Approved Intent-to-Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/OnBuqLuHLeI This CL adds selection/removeRange.html to web-platform-tests. BUG=692881 Review-Url: https://codereview.chromium.org/2710593009 Cr-Commit-Position: refs/heads/master@{#452965} | 24 February 2017, 22:50:13 UTC |
9e1c15f | Domenic Denicola | 24 February 2017, 22:25:58 UTC | Add tests for the realms involved in compiling event handlers Follows https://github.com/whatwg/html/pull/2286 and https://github.com/whatwg/html/issues/2248. | 24 February 2017, 22:25:58 UTC |
7792acc | Chromium WPT Sync | 24 February 2017, 17:10:11 UTC | Merge pull request #5010 from w3c/chromium-export-try Add tests for exiting from nested fullscreen | 24 February 2017, 17:10:11 UTC |
d4e48e5 | foolip | 24 February 2017, 17:00:15 UTC | Add tests for exiting from nested fullscreen Tests for https://github.com/whatwg/fullscreen/pull/72. Before that change, the per-spec pass condition for the nested-in-iframe case would have been to exit fully to the outer document, which was a spec bug and doesn't match implementations. In order to automate these tests, it was necessary to teach auto-click.js to traverse out of iframes to take their position into account. These tests have also been run manually in Firefox Nightly and confirmed to pass there. Actually adopting the new spec wording will be part of relanding issue 402376, together with other necessary spec changes. BUG=402376 Review-Url: https://codereview.chromium.org/2706293013 Cr-Commit-Position: refs/heads/master@{#452841} | 24 February 2017, 17:00:15 UTC |
13aba11 | Chromium WPT Sync | 24 February 2017, 16:50:26 UTC | Merge pull request #5009 from w3c/chromium-export-try Unskip mediastream-capture WPT tests | 24 February 2017, 16:50:26 UTC |
55f035b | rbyers | 24 February 2017, 16:30:15 UTC | Unskip mediastream-capture WPT tests Many of these are passing now. For those that aren't, add -expected.txt files so people notice when causing any new sub-test failures. Renamed MediaStreamTrack-end.https to be a manual test because it relies on user interaction to revoke the permission. Fixed timeout in MediaStream-MediaElement-preload-none.https.html by adding an error handler. Left MediaStreamTrack-MediaElement-disabled-audio-is-silence.https.html skipped due to time-out I couldn't figure out by the end of our WPT hackathon (tracked by http://crbug.com/688613). BUG=412381,688613 Review-Url: https://codereview.chromium.org/2677763002 Cr-Commit-Position: refs/heads/master@{#452840} | 24 February 2017, 16:30:15 UTC |
a7e9c2a | Simon Pieters | 24 February 2017, 08:41:11 UTC | Remove applicationCache in workers/constructors/SharedWorker/global-members.html Follows https://github.com/whatwg/html/pull/2384. | 24 February 2017, 11:09:23 UTC |
f956e38 | Chromium WPT Sync | 24 February 2017, 10:10:10 UTC | Merge pull request #5007 from w3c/chromium-export-try Upstream Blink's 'securitypolicyviolation' tests. | 24 February 2017, 10:10:10 UTC |
aed24e8 | mkwst | 24 February 2017, 09:40:13 UTC | Upstream Blink's 'securitypolicyviolation' tests. Starting on the long slog to get our CSP layout tests more completely upstreamed. This patch leaves most upstream CSP tests disabled, as I still need to go through them in detail, but carves out the 'securitypolicyviolation' directory, moves our local tests over, and ports them to `testharness.js`-style. BUG=695486 Review-Url: https://codereview.chromium.org/2711913003 Cr-Commit-Position: refs/heads/master@{#452780} | 24 February 2017, 09:40:13 UTC |
8b967bb | Mark Nottingham | 24 February 2017, 07:19:25 UTC | Add 304 tests for CORS Per Fetch and HTTP a 304 should be under the same CORS policy as the original 200 (unless it changes it). This is testing to make sure that this is the case, since many servers (including intermediaries) do NOT add CORS headers (and some can't -- e.g., intermediary caches). | 24 February 2017, 07:19:25 UTC |
771007a | Domenic Denicola | 24 February 2017, 04:30:20 UTC | Test that appcache is not supported in shared workers (#5001) Follows https://github.com/whatwg/html/pull/2384. | 24 February 2017, 04:30:20 UTC |
9e5f787 | Chromium WPT Sync | 23 February 2017, 20:50:10 UTC | Merge pull request #5000 from w3c/chromium-export-try WPT tests for allow-top-navigation-by-user-activation for iframe@sandbox. | 23 February 2017, 20:50:10 UTC |
533f802 | binlu | 23 February 2017, 20:40:13 UTC | WPT tests for allow-top-navigation-by-user-activation for iframe@sandbox. Move the test files for disallowing top navigation given no gesture to WPT, and also adding a manual test for allowing top navigation with user gesture. BUG=662506 Review-Url: https://codereview.chromium.org/2711073002 Cr-Commit-Position: refs/heads/master@{#452609} | 23 February 2017, 20:40:13 UTC |
2a40eec | Mike Pennisi | 22 February 2017, 23:26:47 UTC | Stability script: guard against overridden streams | 23 February 2017, 18:45:17 UTC |
236b17b | Joshua Bell | 23 February 2017, 18:25:49 UTC | Add test for StorageManager API vs. opaque origins Entry points (persist(), persisted(), estimate()) should reject in opaque origins (e.g., sandboxed iframes). See https://github.com/whatwg/storage/issues/41. | 23 February 2017, 18:25:49 UTC |
e32ff14 | Daijiro Wachi | 22 February 2017, 21:33:29 UTC | Add blob URLs into urltestdata.json Related link: + https://github.com/nodejs/node/pull/11426 | 23 February 2017, 14:38:54 UTC |
6501418 | James Graham | 23 February 2017, 13:41:48 UTC | Revert "Sort stability test results by execution order" This reverts commit f3921a28b0d013e081c3af661cc71265f74c28c5. | 23 February 2017, 13:58:43 UTC |
291c9a5 | James Graham | 23 February 2017, 13:41:46 UTC | Revert "show list of errors on inconsistent tests" This reverts commit cd87b0d622d55379c229f8c8ea248b39575ad735. | 23 February 2017, 13:58:43 UTC |
0233b5f | James Graham | 23 February 2017, 13:41:40 UTC | Revert "Stability script: reimplement support for timeouts (#4987)" This reverts commit 384c6874f2eeef2841b366d48e5bc80e1f7ee8b3. | 23 February 2017, 13:58:43 UTC |
1f3187f | Anne van Kesteren | 31 January 2017, 12:18:29 UTC | Fetch: casing of header names See https://github.com/whatwg/fetch/pull/476. | 23 February 2017, 10:03:03 UTC |
e29b5db | Anne van Kesteren | 17 February 2017, 13:49:54 UTC | URL: parser failure consistency Fixes #3074. | 23 February 2017, 09:42:31 UTC |
ca35d07 | Simon Pieters | 22 February 2017, 13:45:53 UTC | Expect setting VTTRegion.lines to negative to throw Follows https://github.com/w3c/webvtt/pull/334. Also fix test expectation to match WebIDL's rules for long, and add new tests for NaN etc. | 23 February 2017, 08:59:22 UTC |
436397f | James Graham | 08 May 2015, 12:11:38 UTC | Replace usage of setTimeout with step_timeout in html/webappapis This is expected to help test stability on slow configurations, as the timeouts will be multiplied by the timeout multiplier. | 23 February 2017, 08:06:59 UTC |
e072924 | James Graham | 08 May 2015, 12:11:38 UTC | Replace usage of setTimeout with step_timeout in webvtt This is expected to help test stability on slow configurations, as the timeouts will be multiplied by the timeout multiplier. | 23 February 2017, 08:01:34 UTC |
5c6d05f | Geoffrey Sneddon | 23 February 2017, 01:49:38 UTC | Replace usage of setTimeout with step_timeout in shadow-dom (#4971) This is expected to help test stability on slow configurations, as the timeouts will be multiplied by the timeout multiplier. | 23 February 2017, 01:49:38 UTC |
a3ca332 | Geoffrey Sneddon | 22 February 2017, 22:39:30 UTC | Replace usage of setTimeout with step_timeout in html/syntax (#4982) This is expected to help test stability on slow configurations, as the timeouts will be multiplied by the timeout multiplier. | 22 February 2017, 22:39:30 UTC |
384c687 | jugglinmike | 22 February 2017, 22:36:15 UTC | Stability script: reimplement support for timeouts (#4987) | 22 February 2017, 22:36:15 UTC |
4e2aad5 | jugglinmike | 22 February 2017, 20:04:24 UTC | [html/offline] Avoid race condition in tests At the onset of a given test, the shared application manifest may or may not already be available in the user agent's cache. Because this variability is controlled by external factors (specifically: the previous tests executed in the session), the status of the application cache may not be consistent. Tests whose semantics are effected by this status must therefore explicitly control for the variability in order to exercise the same behavior in all circumstances. Update the test for successful invocation by accounting for both "manifest ready" and "manifest not ready" states. Update the test for unsuccessful invocation by specifying a URL to a non-existent resource. | 22 February 2017, 20:04:24 UTC |
cec5972 | Chromium WPT Sync | 22 February 2017, 19:08:00 UTC | Merge pull request #4957 from w3c/chromium-export-try The security check in document.write should test for same-origin | 22 February 2017, 19:08:00 UTC |
1ea4f53 | Rimas | 22 February 2017, 17:53:27 UTC | URL test fix: "failure" value to be consistently the literal true Fixes two test cases where the "failure" value was the string "true" instead of the boolean. | 22 February 2017, 17:53:27 UTC |
9b41b6d | Geoffrey Sneddon | 22 February 2017, 17:25:46 UTC | Update wpt-tools submodule, add SET TIMEOUT to whitelist (#4960) | 22 February 2017, 17:25:46 UTC |
51f2d6d | Anne van Kesteren | 22 February 2017, 14:33:14 UTC | XMLHttpRequest: text/html sniffing is not used for text (#4935) | 22 February 2017, 14:33:14 UTC |
18be2b8 | Anne van Kesteren | 22 February 2017, 14:30:17 UTC | XMLHttpRequest and <template> (#4927) Fixes #1064. | 22 February 2017, 14:30:17 UTC |
5945fd9 | Anne van Kesteren | 22 February 2017, 13:09:57 UTC | Fetch: make referrer-origin test work on w3c-test.org In particular, this makes it no longer depend on the port being a non-default-port for the scheme. Closes #2618. | 22 February 2017, 14:01:37 UTC |
e7012aa | Anne van Kesteren | 22 February 2017, 13:35:51 UTC | XMLHttpRequest/File API: fetch revoked blob URL Closes https://github.com/whatwg/xhr/issues/79. | 22 February 2017, 13:35:51 UTC |
dabdded | Ms2ger | 22 February 2017, 13:15:26 UTC | Improve request-upload.js In particular: * Reformat request-upload.js. * Consistently use creation functions in request-upload.js. This avoids breaking the test if (for example) ReadableStream is not defined. | 22 February 2017, 13:15:26 UTC |
cba6705 | jochen | 22 February 2017, 13:00:14 UTC | The security check in document.write should test for same-origin Forgot to change this in https://codereview.chromium.org/2691083006 BUG=693819 R=mkwst@chromium.org Review-Url: https://codereview.chromium.org/2707113005 Cr-Commit-Position: refs/heads/master@{#452017} | 22 February 2017, 13:00:14 UTC |
c2cec2f | Benjamin Schaaf | 22 February 2017, 09:30:23 UTC | WebVTT API tests * Renamed webvtt-api-for-browsers/vttcue-interface -> api/VTTCue * Added missing tests to api/VTTCue * Fixed IndexSizeError not being tested for properly * Implemented tests for VTTRegion | 22 February 2017, 09:30:23 UTC |
5e11bf5 | Chromium WPT Sync | 22 February 2017, 08:40:10 UTC | Merge pull request #4952 from w3c/chromium-export-try Don't throw when getting selection(Direction|Start|End) on input | 22 February 2017, 08:40:10 UTC |
540b96c | ratsunny | 22 February 2017, 08:30:14 UTC | Don't throw when getting selection(Direction|Start|End) on input Return null instead of throwing |InvalidStateError| for visiting |selectionDirection|, |selectionStart| and |selectionEnd| on |input| which does not apply selection API. Firefox has the similar behavior. Spec: https://html.spec.whatwg.org/multipage/forms.html#dom-textarea/input-selectionstart This change fix 25 fails in layout tests. BUG=622679 Review-Url: https://codereview.chromium.org/2706033004 Cr-Commit-Position: refs/heads/master@{#451926} | 22 February 2017, 08:30:14 UTC |
e8aa61d | Anne van Kesteren | 17 February 2017, 13:07:35 UTC | URL: test setters with javascript URLs See https://github.com/whatwg/url/pull/254 and https://github.com/whatwg/html/pull/2371 for changes to the standards. | 22 February 2017, 06:15:43 UTC |
8c1d027 | Mike Pennisi | 17 February 2017, 00:00:59 UTC | [html] Avoid race condition in test | 21 February 2017, 21:46:55 UTC |
fdb80c1 | Navid Zolghadr | 21 February 2017, 21:35:44 UTC | Add click event target tests during pointerevent capture (#4763) * Add click event target tests during pointerevent capture plus its ordering compare to lostpointercapture event * Add the click target test with no capture | 21 February 2017, 21:35:44 UTC |
9d4cca4 | jugglinmike | 21 February 2017, 21:22:02 UTC | [html] Account for bug that causes instability The Chromium browser currently implements incorrect semantics regarding the `sheet` property of the `link` element. Defer assertions until such time as incorrect behavior is known to be observable. | 21 February 2017, 21:22:02 UTC |
cd87b0d | Bob Holt | 17 February 2017, 14:24:27 UTC | show list of errors on inconsistent tests | 21 February 2017, 21:12:50 UTC |
f3921a2 | Mike Pennisi | 04 February 2017, 01:31:25 UTC | Sort stability test results by execution order | 21 February 2017, 21:12:50 UTC |
9e33ff6 | Chromium WPT Sync | 21 February 2017, 20:40:09 UTC | Merge pull request #4947 from w3c/chromium-export-try selection: Update Selection interface definition for the 20161206 draft. | 21 February 2017, 20:40:09 UTC |
61b162d | tkent | 21 February 2017, 20:30:14 UTC | selection: Update Selection interface definition for the 20161206 draft. This CL adds 13 tests, and reduces FAILs by 4. BUG=391673 Review-Url: https://codereview.chromium.org/2703293002 Cr-Commit-Position: refs/heads/master@{#451694} | 21 February 2017, 20:30:14 UTC |
652693d | Chromium WPT Sync | 21 February 2017, 20:20:10 UTC | Merge pull request #4946 from w3c/chromium-export-try selection: Do not run invalid sub-tests with unselectable endpoints. | 21 February 2017, 20:20:10 UTC |
69ff91c | tkent | 21 February 2017, 20:10:15 UTC | selection: Do not run invalid sub-tests with unselectable endpoints. collapseToStartEnd.html and isCollapsed.html assumed addRange() with nodes in different roots succeeded. It's not consistent with the latest draft. This CL removes 90 invalid tests, and removes 1 duplicated test for null endpoints. BUG=683066 Review-Url: https://codereview.chromium.org/2709623002 Cr-Commit-Position: refs/heads/master@{#451686} | 21 February 2017, 20:10:15 UTC |
99a1f51 | Anne van Kesteren | 21 February 2017, 20:06:38 UTC | XMLHttpRequest: spell XMLHttpRequest correctly (and modernize a bit) (#4937) | 21 February 2017, 20:06:38 UTC |
976b4d9 | Chromium WPT Sync | 21 February 2017, 20:00:11 UTC | Merge pull request #4945 from w3c/chromium-export-try Media Capabilities: update Blink implementation and WPT to match latest spec changes. | 21 February 2017, 20:00:11 UTC |
3e73186 | mlamouri | 21 February 2017, 19:50:20 UTC | Media Capabilities: update Blink implementation and WPT to match latest spec changes. Changes are: - s/type/contentType/ in {Audio/Video}Configuration; - add [SameObject] to partial Navigator interfaces; - rename "MediaSource" enum entry to "media-source". This is also adding more tests for checks of valid MediaConfiguration.type when running query(). BUG=690380 R=chcunningham@chromium.org Review-Url: https://codereview.chromium.org/2706093002 Cr-Commit-Position: refs/heads/master@{#451669} | 21 February 2017, 19:50:20 UTC |
cffeaba | Chromium WPT Sync | 21 February 2017, 19:40:10 UTC | Merge pull request #4943 from w3c/chromium-export-try selection: Do not run invalid sub-tests with unselectable endpoints. | 21 February 2017, 19:40:10 UTC |
0afc094 | tkent | 21 February 2017, 19:18:02 UTC | selection: Do not run invalid sub-tests with unselectable endpoints. * addRange.js: It assumes any Range can be added to Selection. However the latest draft defines that addRange() rejects Ranges in a root different from Selection's document. Some tests after addRange() with such Ranges were invalid. https://w3c.github.io/selection-api/#dom-selection-addrange > The method must set the context object's range to range by a > strong reference (not by making a copy) if the root ([DOM4]) of > the range's boundary points are the document associated with > context object. Otherwise, this method must do nothing. * exntend.js extend() requires rangeCount>=1. setSelectionForwards() and setSelectionBackwards() are assumed to ensure it. However, these function can't set specified endpoints if they are in roots different from Selection's document. We should skip such endpoints. This CL removes 25,200 invalid tests. BUG=683066 Review-Url: https://codereview.chromium.org/2700673005 Cr-Commit-Position: refs/heads/master@{#451545} | 21 February 2017, 19:18:02 UTC |
18a3faa | wisniewskit | 21 February 2017, 18:50:40 UTC | Add wisniewskit as an owner for XMLHttpRequest (#4942) | 21 February 2017, 18:50:40 UTC |
17b2988 | Anne van Kesteren | 21 February 2017, 10:57:57 UTC | XMLHttpRequest: fix data URL test Fixes #3738. | 21 February 2017, 18:11:36 UTC |
4424ce5 | jugglinmike | 21 February 2017, 17:56:36 UTC | [service-workers] Avoid race condition in test (#4879) The parent document in this test first sends a message to the ServiceWorker and later triggers a `fetch` event. Prior to this commit, the test initiated these two operations independently but required that the Service Worker's `onmessage` handler was invoked prior to its `onfetch` handler. However, because user agents may define independent task queues for `fetch` and `postMessage` [1], there the sequence in which the tasks are handled is not guaranteed. By incorrectly assuming the determinacy of event order, the test created a race condition in user agents that maintain two queues. Re-factor the test to force a consistent execution order. [1] From https://html.spec.whatwg.org/multipage/webappapis.html#task-queue > Each task is defined as coming from a specific task source. All the > tasks from one particular task source and destined to a particular > event loop (e.g. the callbacks generated by timers of a Document, the > events fired for mouse movements over that Document, the tasks queued > for the parser of that Document) must always be added to the same task > queue, but tasks from different task sources may be placed in > different task queues. | 21 February 2017, 17:56:36 UTC |
a0796e9 | Anne van Kesteren | 21 February 2017, 14:20:02 UTC | CORS: replace setTimeout usage (#4938) See #1816. | 21 February 2017, 14:20:02 UTC |
b9731da | Anne van Kesteren | 21 February 2017, 14:18:36 UTC | XMLHttpRequest: use step_timeout more (#4931) Also remove various broken URLs and update some code to be a bit more modern. See #1816. | 21 February 2017, 14:18:36 UTC |
eb6796c | Anne van Kesteren | 21 February 2017, 13:50:23 UTC | CORS: fix broken rel=help URLs | 21 February 2017, 14:04:25 UTC |
dd74df2 | Anne van Kesteren | 21 February 2017, 13:00:45 UTC | Help out with Fetch, URL, and XMLHttpRequest test review | 21 February 2017, 13:04:39 UTC |