https://github.com/web-platform-tests/wpt

sort by:
Revision Author Date Message Commit Date
4bb0ffc HTML: test fieldset content before legend 03 September 2018, 13:45:20 UTC
f50337b Multicol width tests (#11802) * tidying up rule shorthand test, adding assert * Cleanup of existing multicol column-width tests 03 September 2018, 12:22:28 UTC
eeba9d3 tidying up rule shorthand test, adding assert (#11785) 03 September 2018, 12:21:56 UTC
395d964 Implement script MIME restrictions for goal parameter (#8094) This adds tests regarding scripts with a specified goal parameter https://github.com/whatwg/html/pull/3205 03 September 2018, 12:17:18 UTC
84097c6 [eme] Ensure license is expired before using it (#8623) This test generates a license that expires 1s from the current time, calls update() with it, and then waits for 5s before calling play(). However, Chrome caches a few frames in advance of play() being called. Depending on the time granularity, the CDM may see a valid license and decode part of the media file. This change delays calling update() for 2s to ensure that the license has expired, and ensures that the browser can't cache frames to use when play() is called. 03 September 2018, 12:14:05 UTC
e4118eb HTML: test fieldset overflow rendering Bugs: https://bugs.chromium.org/p/chromium/issues/detail?id=786475 https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18694230/ 03 September 2018, 12:09:58 UTC
3a58de9 Fix missing close bracket in css/css-writing-modes/svg-aliasing-001.html (#12788) 03 September 2018, 11:21:32 UTC
6fe0cfa Impose strict MIME-type checks on `importScripts()`. Intent to Remove: https://groups.google.com/a/chromium.org/d/msg/blink-dev/35t5cJQ3J_Q/FH45dl0vAwAJ Bug: 794548, 879994 Change-Id: Ie87aedd0027921960ff429d5d8ecf168572c82de Reviewed-on: https://chromium-review.googlesource.com/1199068 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#588364} 03 September 2018, 10:41:28 UTC
8cc024c [wptrunner] Parameterize Sauce Connect timeout Parameterize the maximum delay so that consumers may select an appropriate value according to their connection and the current performance of the Sauce Labs service. 03 September 2018, 10:18:33 UTC
f4bc725 Merge pull request #12796 from web-platform-tests/sync_4aa068290092afedbfe25c725d89274d78bf6928 Merge pull request #12796 from sync_4aa068290092afedbfe25c725d89274d78bf6928 03 September 2018, 03:30:50 UTC
4aa0682 Mark /css/css-transitions/transitions-animatable-properties-01.html as timeout=long Upstreamed from https://github.com/servo/servo/pull/21580 [ci skip] 03 September 2018, 03:30:40 UTC
0313d9f [Image Capture] Add focusDistance constraint. This CL adds focusDistance to ImageCapture API. This was added to the spec in https://github.com/w3c/mediacapture-image/pull/175 Layout tests and mock tests are updated to support the same. Support for Android is added. TEST= run the demo in https://codepen.io/rijuB/pen/NzWpxG use slider to change focusDistance. BUG=732807 Intent to Implement and Ship discussions: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/oNxzXaFY9c8 Change-Id: I9b7cbf3c85fd35741a8c7ed229910a996e14ee8f Reviewed-on: https://chromium-review.googlesource.com/1124839 Reviewed-by: Miguel Casas <mcasas@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Cr-Commit-Position: refs/heads/master@{#588299} 03 September 2018, 01:21:58 UTC
3fd70a9 Make syntax highlight for code block 02 September 2018, 09:24:41 UTC
82d6797 Merge pull request #12782 from fippo/test-as-you-commit webrtc: throw SyntaxError on {iceServers: []} 01 September 2018, 17:07:17 UTC
0588fa3 Merge pull request #12793 from web-platform-tests/sync_a56619e7fb09a02b032e4acab5cd7704bd242ae3 Merge pull request #12793 from sync_a56619e7fb09a02b032e4acab5cd7704bd242ae3 01 September 2018, 14:23:16 UTC
ab98b1b Merge pull request #12792 from web-platform-tests/sync_1ce329cb195c77b3d26cb1cadc75aecef7d33728 Merge pull request #12792 from sync_1ce329cb195c77b3d26cb1cadc75aecef7d33728 01 September 2018, 14:22:58 UTC
1ce329c Add tests for options bounds in PannerNode's constructor Upstreamed from https://github.com/servo/servo/pull/21555 [ci skip] 01 September 2018, 14:22:49 UTC
a56619e correct failing tests Upstreamed from https://github.com/servo/servo/pull/21533 [ci skip] 01 September 2018, 14:22:49 UTC
268ce53 Upstream the tests from bug 488725. Differential Revision: https://phabricator.services.mozilla.com/D4076 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1485669 gecko-commit: 6932f13cab4b201c3f1501adce7ef43b23ca80b0 gecko-integration-branch: autoland gecko-reviewers: dbaron 01 September 2018, 09:40:03 UTC
f1c3743 [PE] Fix LayoutBox Client/Padding/Content boxes with scrollbars (especially vertical-rl) This CL tries to correct the box model when there are scrollbars, especially in vertical-rl mode. According to https://www.w3.org/TR/css-overflow-3/#scrollbar-layout, scrollbars "should be inserted between the inner border edge and the outer padding edge". Changes to the previous code: - Padding|client box now excludes scrollbars, with the help of (Top|Left|Bottom|Right)ScrollbarWidth methods which can get the scrollbar widths in physical directions in various writing modes. - Content box is now based on the new padding box by excluding the paddings. - Layout of contents is now based on the correct box model. In vertical-rl mode, layout of contents in blocks direction starts from the inner edge of the new content box which has been properly adjusted for the scrollbar. - Now LayoutBox::Location() and Location::PhysicalLocation() in the initial scroll state are correct in all writing-modes. Previously when they were incorrect in vertical-rl mode and some flex box directions, requiring an artificial scroll offset to paint the content at correct place. - With the correct padding box, content box, Location(), PhysicalLocation(), we no longer need the band-aid code to create the correct painted result. The changed code is mostly in LegacyLayout code. Some changed code is in LayoutNG that previously converted correct LayoutNG geometries into the problematic geometries that were previously expected by LegacyLayout. The correct box model is required by blink-gen-property-trees because we can't band-aid the incorrect results in paint properties after painting. Bug: 833167,853945,858843,878809,876266 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:linux_layout_tests_layout_ng;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I41faf1ca0bfb95cb287c72703f08c8bd44e9e752 Reviewed-on: https://chromium-review.googlesource.com/1185901 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#588201} 31 August 2018, 23:32:42 UTC
2b7dace Add observable settings for getDisplayMedia() This CL adds observable settings to MediaStreamTrack objects returned by getDisplayMedia() calls. These constrainable properties are set before the stream is returned based on user choice. Information about these settings are stored in DisplayMediaInformation struct. It is set in the low level device selection and then parsed by UserMediaProcessor before passing it to blink. Bug: 326740 Change-Id: I81d5f2eb24d2c1a37df0fbe2d34bc469fa575bf1 Reviewed-on: https://chromium-review.googlesource.com/1185875 Reviewed-by: Tom Sepez <tsepez@chromium.org> Reviewed-by: Dan Sanders <sandersd@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Weiyong Yao <braveyao@chromium.org> Commit-Queue: Emircan Uysaler <emircan@chromium.org> Cr-Commit-Position: refs/heads/master@{#588162} 31 August 2018, 21:25:36 UTC
b9f0af2 Add validation to the requestDevice filters This change adds validation checks to the USBDeviceFilter parameters passed into navigator.usb.requestDevice. Bug: 854703 Change-Id: I921a7f30a9e2ec5d46d3a74801de594565ab8a6f Reviewed-on: https://chromium-review.googlesource.com/1196034 Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#588140} 31 August 2018, 20:33:03 UTC
3a396df Merge pull request #12786 from fippo/fix-offeroptions webrtc: fix no-media-call 31 August 2018, 20:24:51 UTC
2142014 Fix a test case and add more test cases for overlapping SetValueCurveAtTime. Differential Revision: https://phabricator.services.mozilla.com/D4107 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1308436 gecko-commit: 1c8691a860201bec454a968097ebb4f63a0f4f66 gecko-integration-branch: mozilla-inbound gecko-reviewers: karlt 31 August 2018, 19:32:12 UTC
e4a0aa6 Fix typo in audioparam-setValueCurve-exceptions.html. Differential Revision: https://phabricator.services.mozilla.com/D4101 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1308436 gecko-commit: 9ad67bac864379a1784263b61fd084412673ced4 gecko-integration-branch: mozilla-inbound gecko-reviewers: karlt 31 August 2018, 19:32:12 UTC
91e7172 Add a test case for a negative curve duration in audioparam-exceptional-values.html. Differential Revision: https://phabricator.services.mozilla.com/D4098 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1308436 gecko-commit: 08897a32ca0578a8bc14722824fe5d0f187936de gecko-integration-branch: mozilla-inbound gecko-reviewers: karlt 31 August 2018, 19:32:12 UTC
c6fd45b webrtc: fix no-media-call the legacy offer options need to be passed to createOffer, not the then. regression from #12715, caused chrome to fail on import 31 August 2018, 18:58:00 UTC
6bde19a Move Autoplay feature policy tests to html dir Change-Id: I2b60a751ad4c3ad87e6a9e75d55e2f96698e88b9 Reviewed-on: https://chromium-review.googlesource.com/1198571 Reviewed-by: Becca Hughes <beccahughes@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#588041} 31 August 2018, 16:29:37 UTC
b81e490 [LayoutNG] Fix when 'vertical-align: top' is nested The 'vertical-align: top' and 'bottom' require the size of the ancestor line box and thus are put into pending queue while applying the baseline shift. When they are nested, processing all pending queue at the root line box applies the shift multiple times. This patch puts into the queue of the nearest ancestor that has 'top' or 'bottom' if exists. Bug: 877977 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I6541d138267a6e42658b601901b673352e625440 Reviewed-on: https://chromium-review.googlesource.com/1198887 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#588042} 31 August 2018, 16:20:34 UTC
95ad2a0 webrtc: throw SyntaxError on {iceServers: []} test-as-you-commit for https://github.com/w3c/webrtc-pc/pull/1978 31 August 2018, 15:15:44 UTC
490ffff HTML: support display: list-item on legend See https://github.com/whatwg/html/issues/3969 31 August 2018, 14:25:23 UTC
8aa4853 Add "intrinsicSize" attribute to HTMLVideoElement behind a flag This CL is based on: https://chromium-review.googlesource.com/c/chromium/src/+/1150725 Design doc: https://docs.google.com/document/d/1yh_-ayeaFV0EjuR51U641zbrPAB0Baqj6UrC9bT9iqQ/edit#heading=h.y7amr11fn0tb This CL implements "intrinsicSize" attribute for HTMLVideoElement. The value of "intrinsicSize" overrides the intrinsic size: 1. When no width and (or) height is specified, the value of "intrinsicSize" will be used to determine the area to layout the video content. 2. videoWidth and videoHeight will return the value defined by "intrinsicSize". See explainer: https://github.com/ojanvafai/intrinsicsize-attribute/blob/master/README.md Bug: 874629 Change-Id: If4aeceee2299c50aa7b4c9bdf8fef7cb3e7eea70 Reviewed-on: https://chromium-review.googlesource.com/1191926 Commit-Queue: Luna Lu <loonybear@chromium.org> Reviewed-by: Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#587667} 31 August 2018, 14:21:09 UTC
557602e Add RTCQuicStream IDL + binding skeleton Bug: 868068 Change-Id: I339a79b5709425b2e7d0d4d50f0bfa0602afc7ab Reviewed-on: https://chromium-review.googlesource.com/1170171 Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Steve Anton <steveanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#587669} 31 August 2018, 14:19:32 UTC
2d8be4b Capitalize WebdriverSpecTest => WebDriverSpecTest This was the only class capitalized like this, and the only occurences of "Webdriver" anywhere in the repo. For consistency with classes WebDriverException, WebDriverProtocol and WebDriverServer. 31 August 2018, 14:14:02 UTC
4fd41de Fix the error catching logic of should().throw() in audit.js Context: https://github.com/web-platform-tests/wpt/pull/12606 Change the logic of should.throw() so we can handle 3 cases - should(someExpression).throw(); should(someExpression).throw(TypeError); should(someExpression).throw(DOMException, 'NotSupportedError'); The generic error (except for DOMException) can be passed without the second argument, but this change will enforce the second arg when the expected error is a DOMException type. This touches many test files, so the work will be done in several steps: 1. Change audit.js, audionodeoptions.js on both locations. (wpt, non-wpt) 2. Update affected test files with the script. 3. Update the rest of test files which can't be updated programmatically. Bug: 865614 Test: All layout tests pass. Change-Id: I16acacb26c194a0ff950aca05e931195bf55167f Reviewed-on: https://chromium-review.googlesource.com/1184146 Commit-Queue: Hongchan Choi <hongchan@chromium.org> Reviewed-by: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#587660} 31 August 2018, 14:13:51 UTC
6955f7b [css-properties-values-api] Typify CSSStyleValue.parse/All. Passing the PropertyRegistration makes StyleValueFactory::FromString find the typed value, and create appropriate and corresponding TypedOM types. Note: the check on property_id==CSSPropertyVariable isn't strictly required, but it's nice to avoid the AtomicString creation if we know it's not needed. R=futhark@chromium.org Bug: 641877 Change-Id: Id7f7f8c754f8aab7f64a92efd896243858d03757 Reviewed-on: https://chromium-review.googlesource.com/1199182 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#588001} 31 August 2018, 13:02:59 UTC
1692453 Import all remaining cookie tests into WPT This CL adds all remaining tests from https://github.com/abarth/http-state/tree/master/tests. Not all of them pass, but all of them run consistently with the same results. This also adds a lot of documentation - in code and when running a server. By navigating to <server>/cookies/http-state/resources/cookie-setter.py All tests are gathered and run. The shown document explains the usage of the server for debugging purposes. Change-Id: I4a75655704dddc213a3f3b6fa26beeb14acf3338 Reviewed-on: https://chromium-review.googlesource.com/1021577 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Friedrich Horschig <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#583606} 31 August 2018, 08:19:26 UTC
542fc6e Merge pull request #12668 from mstensho/multicol-span-inline-block Add test for specifying column-span:all on an inline-block. 31 August 2018, 06:23:38 UTC
04a1106 Fix textBaseline alignment to match the spec for top/bottom/middle. Our current implementation of canvas textBaseline alignment for top middle and bottom doesn't do what the spec says it should, i.e. align with the EM square. https://html.spec.whatwg.org/multipage/canvas.html#dom-context-2d-textbaseline This has been a bug on FF side for quite some years: https://bugzilla.mozilla.org/show_bug.cgi?id=737852 This change fixes this misalignment by using the EM square ascent and descent from SimpleFontData instead of the font's max ascent/descent. Also fixing the EM related metrics in canvas TextMetrics. Bug:607053,277215 Change-Id: Id6374e6fcd4e46fa989a7e23a80dc1f5bf961b94 Reviewed-on: https://chromium-review.googlesource.com/1194494 Commit-Queue: David Quiroz Marin <davidqu@chromium.org> Reviewed-by: Fernando Serboncini <fserb@chromium.org> Cr-Commit-Position: refs/heads/master@{#587855} 31 August 2018, 00:15:57 UTC
6968641 Storage API: Register "persistent-storage" permission string The Storage API [1] defines the "persistent-storage" string to allow querying the state of the permission. Plug this into the Permission API [2] implementation and add a web platform test. [1] https://storage.spec.whatwg.org/ [2] https://w3c.github.io/permissions Intent to Ship: https://groups.google.com/a/chromium.org/d/topic/blink-dev/FRAmGlAoDTY/discussion ChromeStatus: https://www.chromestatus.com/feature/4770049554382848 Bug: 878525 Change-Id: Ia12fb43676e04e7e60ad58b5ffbd7ee22f78ffc4 Reviewed-on: https://chromium-review.googlesource.com/1194106 Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#587839} 30 August 2018, 23:48:41 UTC
16e4b91 [css-grid] Compute again the baseline offsets during step 3 The new Baseline Alignment algorithm states that items with sizing cyclic dependencies must be excluded from any baseline context they participate in. One of these cyclic dependencies can happen with intrinsic sized grid areas and relative items. The grid spec states [1] that flex-sized tracks should be considered as content-sized when the grid container has an indefinite size. We were using the AvailableSize(direction) function to determine whether the grid container is indefinite or not. However, this function may provide different results during the different phases of the grid layout logic. This issue causes assert violations like the one described in the bugs listed below. The new Baseline Alignment logic is now integrated in the Grid Track sizing algorithm. Hence, we need to ensure that an item that participates in any baseline alignment context during the track sizing also does during the alignment phase, at the end of the grid layout logic. In order to achieve that, this CL forces a new computation of the Baseline offsets during the step 3 of the Grid sizing algorith, since during this step the available space is not indefinite anymore. It's worth mentioning that this change assumes the issue grid items being excluded and included of Baseline Context during the different phases of the Grid sizing algorithm, which I hope we can clarify in the issue [2] I filed for the CSS WG. [1] https://drafts.csswg.org/css-grid/#fr-unit [2] https://github.com/w3c/csswg-drafts/issues/3046 Bug: 867833, 874861, 876593 Change-Id: I668d399b920c9280a8e20b3e8362f562eded4770 Reviewed-on: https://chromium-review.googlesource.com/1177757 Reviewed-by: Sergio Villar <svillar@igalia.com> Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#587799} 30 August 2018, 22:19:46 UTC
8c12648 HTMLImageElement intrinsicSize attribute override intrinsic aspect ratio for responsive images The CL https://chromium.googlesource.com/chromium/src/+/bd4c33b5e81d495ecdac66b0375924d9565330cb did not handle responsive images correctly. This CL resets overridden_intrinsic_size_: When source is chosen using W descriptor, 'sizes' sets the new width of the overridden_intrinsic_size_, and the new height is calculated by the aspect ratio defined by the intrinsicSize attribute. Bug: 874629 Change-Id: I16b2f6c2fb9ae741144ba509c57f1e033c8cdc17 Reviewed-on: https://chromium-review.googlesource.com/1195801 Commit-Queue: Luna Lu <loonybear@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#587774} 30 August 2018, 21:43:30 UTC
8ff2bb6 [Blink] Remove negative offset compensation for rel-pos inline Consider the following case: <span style="position:relative; left:-100px;"> <div style="display:inline-block; position:absolute;"></div> </span> In our implementation the absolute positioned element will have a counter offset applied, to ignore the negative offset on its rel-pos parent. The compensation was added in https://codereview.chromium.org/423173003/ which wasn't covered by the added test, and isn't consistent with other browser implementations. (Checked with Safari, IE, and Firefox.) BUG=398164 Change-Id: I44127ff42446a7483d7e4ebb3197ecdc915db39d Reviewed-on: https://chromium-review.googlesource.com/1195084 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Tien-Ren Chen <trchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#587745} 30 August 2018, 20:58:01 UTC
9b90762 Extend wasm js-api tests bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486000 gecko-commit: 18c0aff587fa935a8149f83d58664e77c35e598a gecko-integration-branch: mozilla-inbound gecko-reviewers: bbouvier 30 August 2018, 18:02:16 UTC
d6ab2e6 Enable FP reporting for WebMIDI policy violations. This queues a report through the Reporting API whenever navigator.requestMIDIAccess is invoked from a frame in which the 'midi`' feature is not allowed according to feature policy. Bug: 867471 Change-Id: Ib7966a3721067fcf7a325d75377178caaa4b327a Reviewed-on: https://chromium-review.googlesource.com/1195703 Commit-Queue: Ian Clelland <iclelland@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#587617} 30 August 2018, 16:59:28 UTC
0302b22 tests for MerchantValidationEvent (#12424) * tests for MerchantValidationEvent * contructor tests, including validationURL * complete() method * Test fixup 30 August 2018, 16:17:11 UTC
36b0fe7 Fix reftest chain comparisons in marionette reftest implementation We were previously using the original test url as the lhs for each comparison after the top level, rather than the previous rhs url as expected. Differential Revision: https://phabricator.services.mozilla.com/D4081 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1485668 gecko-commit: 0cd882a506cfa9c7489160d06437361430e0aa65 gecko-integration-branch: autoland gecko-reviewers: ato 30 August 2018, 15:54:47 UTC
cf66d92 [wdspec] Create tests for "Is Element Enabled" command. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486572 gecko-commit: 3eb891993d3e0802ae958cb8256d4e44c3b0817e gecko-integration-branch: mozilla-inbound 30 August 2018, 15:41:02 UTC
ffe0601 [wdspec] Improve timeouts tests for "Set Timeout" and "New Session". bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1485580 gecko-commit: 1fd335726c0088e8ffe303beff533442c973b083 gecko-integration-branch: mozilla-inbound gecko-reviewers: jgraham 30 August 2018, 15:39:18 UTC
0f676ec Change ErrorStatus::{ScriptTimeout,Timeout} HTTP codes from 408 to 500. Whilst it is logically correct to use 408 for the ErrorStatus::ScriptTimeout and ::Timeout errors, it causes a collision with HTTP semantics implement in HTTP clients. To support Keep-Alive we allow retries in HTTP clients and if a client sees code 408 it thinks that the server has gone away and retries the request. This causes WebDriverCommand::ExecuteScript, ::Get, and ::Refresh commands to be sent twice with some HTTP clients. This is a backwards incompatible change to WebDriver in order to not break HTTP/1.1 Keep-Alive. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1484941 gecko-commit: 72a737dd8639ab72ddc96d1144f44b06507b915e gecko-integration-branch: mozilla-inbound gecko-reviewers: whimboo 30 August 2018, 15:38:43 UTC
3f04608 Enable FP reporting for sync-xhr violations. This queues a report through the Reporting API whenever send() is called on a synchronous XMLHttpRequest object from a frame in which sync-xhr is not allowed according to feature policy. Bug: 867471 Change-Id: If778ea5517fb5728992fe8287b278d1af729902f Reviewed-on: https://chromium-review.googlesource.com/1191404 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#587583} 30 August 2018, 15:37:19 UTC
ebd7877 Upstream image_capture tests to WPT Moved the layout tests under third_party/WebKit/LayoutTests/imagecapture/ to third_party/WebKit/LayoutTests/external/wpt/mediacapture-image/ Moved the layout tests under fast/imagecapture to wpt and suffixed some file names with -fast.html to avoid name collision. ImageCapture-creation.html was renamed to ImageCapture-creation.https.html as it needed to be served over https Moved third_party/WebKit/LayoutTests/imagecapture/resources/imagecapture-helpers.js to third_party/WebKit/LayoutTests/external/wpt/mediacapture-image/resources/imagecapture-helpers.js and extended it by adding a wrapper promise test, image_capture_test. Copy the auto generated image_capture.mojom.js to wpt/resources/chromium/mock-imagecapture.js used a flag called "scramble_message_ids = false" to the mojom compiler. Used the testharness from wpt/ No new tests have been added. BUG=706434 Cq-Include-Trybots: luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I7de5b87b60396da841dda490da02bce800fcb793 Reviewed-on: https://chromium-review.googlesource.com/1165355 Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Miguel Casas <mcasas@chromium.org> Commit-Queue: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Cr-Commit-Position: refs/heads/master@{#587144} 30 August 2018, 15:17:38 UTC
51ad2f3 Notify andruud on changes to wpt/css/css-properties-values-api. Also remove author from tests. The commit log is more reliable anyway. R=foolip@chromium.org Change-Id: Ibd5a9f7089a8d10bbe77db071b2e1147b05817f4 Reviewed-on: https://chromium-review.googlesource.com/1196429 Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#587548} 30 August 2018, 15:01:36 UTC
b0e04b7 Make wpt run's hosts file check fail properly on Windows (#12759) Previously it threw ValueError due to the unescaped % in the error message. 30 August 2018, 14:38:33 UTC
241cb91 Refactored usage of XHR, added error handling. - Added error handling as suggested in https://github.com/web-platform-tests/wpt/pull/12162 - changed XHR calls to FetchAPI - changed async tests to Promise tests - corrected the existing redirect tests and reported bug: crbug/872285 - removed Same-Site and Cross-Origin XSLT tests as they seemed to fail because loading cross origin xslt is not supported "Unsafe attempt to load URL from frame" (No idea why they passed before) - added two test cases for multiple redirects. The idea is that the Sec-Metadata header should be "downgraded" to less secure and should carry the value to the end. If a cross-origin domain controls a redirect at any point of the redirect chain, then the final requests are potentially influenced by the attacker. - (Same-Origin -> Cross-Site -> Same-Origin -> Same-Origin) -> site=cross-site - (Same-Origin -> Same-Site -> Same-Origin -> Same-Origin) -> site=same-site Change-Id: I591af1948cc1f16e3b5c44f51020149e43fc2746 Reviewed-on: https://chromium-review.googlesource.com/1193953 Commit-Queue: Maciek Trzos <mtrzos@google.com> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#587556} 30 August 2018, 14:30:32 UTC
335a7e0 Add comment describing shared lock for NEL tests 30 August 2018, 13:46:30 UTC
2aa0132 Fix bugs in the network-error-logging lock handler. It's not clear to me if this is a good way to use the stash, but at least it doesn't throw anymore. 30 August 2018, 13:46:30 UTC
d9bcf59 [css-properties-values-api] Support string values in StylePropertyMap.set. When producing a CSSStyleValue from a string for a registered custom property, parse the value according to the syntax instead of always creating a CSSUnparsedValue. Note that <color> and <url> are still not supported, because CSSUnsupportedProperty does not work properly for registered custom properties (yet). R=futhark@chromium.org Bug: 641877 Change-Id: I806eb5b0c5112956e34457808791367423587c76 Reviewed-on: https://chromium-review.googlesource.com/1177755 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#587537} 30 August 2018, 13:24:17 UTC
b671cd0 Remove 'cookies/secure/create-cookie-http.html' This test is broken; every browser fails it in the same way, and the thing it actually intends to cover is addressed by the other six tests in https://wpt.fyi/results/cookies/secure. Change-Id: Ib7b8534b35ae16490f2cf71e67936b5636e33fbe Reviewed-on: https://chromium-review.googlesource.com/1196544 Reviewed-by: Friedrich Horschig [CEST] <fhorschig@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#587535} 30 August 2018, 13:24:13 UTC
3c7a5ab TrustedTypes: Added TrustedTypes.getExposedPolicy(name) & minor changes Added TrustedTypes.getExposedPolicy(name) and bool exposed in TrustedTypePolicyOptions Added test Changed Vector of created policies into Map of created policies Bug: 739170 Change-Id: Ib5fe7a14ddadb88e3de70ee55f2783b9d10a01b5 Reviewed-on: https://chromium-review.googlesource.com/1193869 Commit-Queue: Orsolya Bernadett Batiz <orsibatiz@google.com> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#587534} 30 August 2018, 13:14:30 UTC
7078352 Remove ad-hoc CORS logic from TextTrackLoader As specified in [1], it should use "same-origin" request mode rather than having ad-hoc CORS logic in TextTrackLoader. Now a response from service worker with type "cors" is rejected. The new behavior is actually more spec compliant (and matching with Firfox), so fix the corresponding web platform test. 1: https://html.spec.whatwg.org/multipage/media.html#start-the-track-processing-model Bug: 875153 Change-Id: Ib39ed9684528d734c9ca3d40eb8f6890c77af986 Reviewed-on: https://chromium-review.googlesource.com/1195446 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#587492} 30 August 2018, 09:59:33 UTC
12c5fcb Move inert tests to top level directory and rename with .tentative Remove duplicate test which ended up in editing/focus/inert. Bug: 692360 Change-Id: I25571a7e731cd8ce5f1fce85e9d246939b78690b Reviewed-on: https://chromium-review.googlesource.com/1168267 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#587399} 30 August 2018, 02:06:11 UTC
fc6300a Test PaymentRequest onmerchantvalidation attribute (#12423) 30 August 2018, 01:58:02 UTC
40141b4 [wdspec] Add basic tests for "Take Element Screenshot" command. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486793 gecko-commit: 46011d6f389df1f1f41a862c73e59b1716e92e55 gecko-integration-branch: mozilla-inbound gecko-reviewers: ato 30 August 2018, 00:11:11 UTC
074a50d [wdspec] Add basic tests for "Take Screenshot" command. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486793 gecko-commit: e2251ddcafd236d667b5ebb4908429bc88c99de8 gecko-integration-branch: mozilla-inbound gecko-reviewers: ato 30 August 2018, 00:11:11 UTC
a089efa Merge pull request #12715 from youennf/wpt-export-for-webkit-189040 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=189040 29 August 2018, 22:14:59 UTC
1074778 Merge pull request #12743 from emilio/webkit-bug-189089 Add a test for WebKit bug 189089. 29 August 2018, 22:12:25 UTC
99c4f1d Fix one paint containment wpt (incorrect expectations) This patch removes one passing paint containment test expectation. It also fixed an expectation in one other that has an incorrect word s/digit/number/ R=chrishtr@chromium.org Change-Id: I756dc10ff49d7b3ef762d9d9733b566501cb2f5e Reviewed-on: https://chromium-review.googlesource.com/1195678 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#587251} 29 August 2018, 20:09:02 UTC
17627a7 [wdspec] Add test for empty text to send_alert_text/send.py. The patch refactors the test file, and also adds an additional test, which makes sure that the default text of the prompt is replaced in case of an empty string is send as text. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486485 gecko-commit: 82dc592c7293290a7b17c4473c01a228e42615cd gecko-integration-branch: mozilla-inbound gecko-reviewers: jgraham 29 August 2018, 20:05:54 UTC
96e846f Enable FP reporting for unsized-media policy violations. This queues a report through the Reporting API whenever an image is encountered which violates the 'unsized-media' policy, in a document in which that feature is not allowed according to feature policy. Bug: 867471 Change-Id: I8d39639d21d9a993685f97efc078a9a1ab6f303c Reviewed-on: https://chromium-review.googlesource.com/1195675 Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#587236} 29 August 2018, 19:46:43 UTC
cf6f1d4 Add pointerrawmove implementation Push a new PointerRawMove in the main thread event queue for MouseMove events. Note that we do not send compatibility mouse events for this type. Only PointerEvent with the type pointerrawmove. Also note that this change only adds pointerrawmove for mouse events at this point. pointerrawmove for touch events should come in the following CLs. Intent to implement: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/84RGJvm_PMM Bug: 873684 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Icb003b8ba978f1c64157dbbe79222a687d4aa42d Reviewed-on: https://chromium-review.googlesource.com/1181171 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Rick Byers <rbyers@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Ella Ge <eirage@chromium.org> Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#587226} 29 August 2018, 19:46:40 UTC
9bda9c6 Enable FP reporting for payment violations. This queues a report through the Reporing API whenever the PaymentRequest API is invoked from a frame in which the 'payment' feature is not allowed according to feature policy. Bug: 867471 Change-Id: Ie03fe06924a634829d03fb9d9693aee29ab66dd2 Reviewed-on: https://chromium-review.googlesource.com/1191411 Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#587223} 29 August 2018, 19:34:09 UTC
2e742eb Add one more WPT test to cavas TextMetrics for advances. Adding a test to validate that calling measureText a second time, it gives the same results (an arrray with the same values) as a first time. Change-Id: I5308b6610633de2d5ac44d45f07a97d7f63657e5 Reviewed-on: https://chromium-review.googlesource.com/1191536 Reviewed-by: Fernando Serboncini <fserb@chromium.org> Commit-Queue: David Quiroz Marin <davidqu@chromium.org> Cr-Commit-Position: refs/heads/master@{#587196} 29 August 2018, 18:34:56 UTC
1f40395 Add a test for WebKit bug 189089. https://webkit.org/b/189089 29 August 2018, 18:04:36 UTC
9be7cfe Fix fullscreen WPT tests assuming fullscreenElement changes each time. Since fullscreenchange event is sent by the rAF event loop it is possible that the fullscreenElement might change and not be observed at the time you read the event. Fix the tests so they are robust. Fix the ordering of which fullscreen elements are handled in pending frames. Otherwise we might end up with incorrect ordering. BUG=874444 Change-Id: I00c228e0aea7794564e522a3883573ea359235f1 Reviewed-on: https://chromium-review.googlesource.com/1194726 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#587170} 29 August 2018, 17:44:22 UTC
eca7f8c [layoutng] Add a flag for content size vs border box size to ComputeMinMaxSize And use it to simplify and speed up code in LayoutNGBlockFlow Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I56c486b66376497fc89b5c18ee5bbdf910573eb1 Reviewed-on: https://chromium-review.googlesource.com/1195502 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#587154} 29 August 2018, 17:03:43 UTC
99f5891 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=189040 29 August 2018, 16:46:13 UTC
f42b3cc Sync fullscreen Element Ready steps with spec. I discovered the fullscreen element ready steps didn't quite match the spec. Changes https://github.com/whatwg/fullscreen/issues/45 and https://github.com/whatwg/fullscreen/commit/9592913bbeca3a9d029274f310eb27ad8003622c weren't reflected in our implementation. I've modified the tests to match. BUG=627792 Change-Id: Ia0cd0700ea05248d14225d551f3e5287be2b99ef Reviewed-on: https://chromium-review.googlesource.com/1191728 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#587138} 29 August 2018, 16:34:33 UTC
b42438a Add intrinsicsize attribute to HTMLImageElement behind a flag Design doc: https://docs.google.com/document/d/1yh_-ayeaFV0EjuR51U641zbrPAB0Baqj6UrC9bT9iqQ/edit#heading=h.y7amr11fn0tb This CL implements "intrinsicsize" attribute for HTMLImageElement. The value of "intrinsicsize" overrides the intrinsic size: 1. When no width and (or) height is specified, the value of "intrinsicsize" will be used to determine the area to layout the image content. 2. natualWidth and naturalHeight will return the density corrected value of "intrinsicsize". See explainer: https://github.com/ojanvafai/intrinsicsize-attribute/blob/master/README.md BUG: 874629 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I519f01841ee3e761b22874dbecd74f7e6843e2a9 Reviewed-on: https://chromium-review.googlesource.com/1150725 Commit-Queue: Luna Lu <loonybear@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#587132} 29 August 2018, 16:13:56 UTC
fb8c0bf Enable FP reporting for camera and microphone violations. This queues a report through the Reporting API whenever camera or microphone access are requested through getUserMedia, in a frame in which either the 'camera' or 'microphone' features are not allowed according to feature policy. Bug: 867471 Change-Id: Id54caf385f710f02b94010e642c7eb395e6a831f Reviewed-on: https://chromium-review.googlesource.com/1191417 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#587127} 29 August 2018, 16:04:01 UTC
d82155b Avoid scrolling when entering fullscreen When entering fullscreen we shouldn't need to set scroll to 0,0. This fixes fullscreening an element that has scroll offset. BUG=693075,684920 Change-Id: I2acf27eb2641731d580865d38e1a1495f6aee7de Reviewed-on: https://chromium-review.googlesource.com/1191664 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#587120} 29 August 2018, 15:44:46 UTC
01d6bfd Enable FP reporting for fullscreen violations. This queues a report through the Reporting API whenever [webkit]RequestFullscreen is called from a frame in which fullscreen is not allowed according to feature policy. Checking [webkit]fullscreenAllowed does not trigger reports. Bug: 867471 Change-Id: I4e7077aea66246d712e549b79b6154c1a596d74c Reviewed-on: https://chromium-review.googlesource.com/1191482 Commit-Queue: Ian Clelland <iclelland@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#587109} 29 August 2018, 15:34:46 UTC
91e3f8d [serve] Log state of subprocesses during shutdown 29 August 2018, 14:52:14 UTC
1f17212 [serve] Quit on sub-process failure The correctness of the WPT server is dependent on the availability of all server sub-processes. If any sub-process dies, the server is no longer capable of performing its role. Allow the process to exit in this case. Introduce a test for this behavior. 29 August 2018, 14:52:14 UTC
867c430 Merge pull request #7685 from frivoal/widows-orphans-clarification [css-break-3] Basic widows and orphans test 29 August 2018, 14:21:30 UTC
ae16af4 More properties do not accept number Test that various additional properties do not accept <number> in quirks mode. The tests fail if properties are not supported. 29 August 2018, 14:19:27 UTC
1d05106 [wdspec] Add "Execute Script" test for final comment. (#12736) bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1337899 gecko-commit: 068631fb32af4e414f182ff5a24de9240d4bcb7e gecko-integration-branch: central gecko-reviewers: ato 29 August 2018, 13:21:39 UTC
3ede662 Encoding: TextEncoderStream and TextDecoderStream The standard change that adds these classes is https://github.com/whatwg/encoding/pull/149. 29 August 2018, 10:14:14 UTC
d895bcc Add AudioWorklet tests to WPT. Differential Revision: https://phabricator.services.mozilla.com/D4205 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1481676 gecko-commit: 4e424820681656fc761059f904427b7f6c7fe4e7 gecko-integration-branch: autoland gecko-reviewers: karlt 29 August 2018, 09:51:01 UTC
0968712 [wdspec] Create basic tests for "Get Element CSS Value" command. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486495 gecko-commit: 1132c5e406a2a6220f71f54668401a22e6eff3a5 gecko-integration-branch: mozilla-inbound 29 August 2018, 09:41:25 UTC
160ef65 Remove sideshowbarker from html/META.yml 29 August 2018, 07:47:59 UTC
d2cffc6 HTML: document.open() and document's URL (with fragments) For https://github.com/whatwg/html/pull/3970. Co-authored-by: Timothy Gu <timothygu99@gmail.com> 29 August 2018, 07:28:20 UTC
e520aed Enable FP reporting for document-write violations. This queues a report through the Reporting API whenever the dynamic markup insertion methods (document.open, close, write, writeln) are called from a frame in which document-write is not allowed according to feature policy. Bug: 867471 Change-Id: I08bc1c8e96f45a7c8c544df2f9a718880680dc01 Reviewed-on: https://chromium-review.googlesource.com/1191533 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#587003} 29 August 2018, 03:40:42 UTC
1922679 Update WebUSB terminate child context tests This change updates tests for WebUSB where a child context is terminated while having a USB device open. The existing tests are modified to send the MojoHandle intercepted by MojoInterfaceInterceptor through a MessageChannel to allow a new test for a worker context to be created. As a result, the MojoHandle class is made transferable over a MessageChannel. Bug: 841510, 852878 Change-Id: Ib7f74d172b9dcc16a4821a4063cfffc196466a88 Reviewed-on: https://chromium-review.googlesource.com/1162351 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#586942} 29 August 2018, 00:33:26 UTC
66f7d1e Improve Code Coverage for WebUSB This change improves the code coverage for the sources files under //third_party/blink/renderer/modules/webusb. The affected files are: * usb.cc * usb_alternate_interface.cc * usb_configuration.cc * usb_device.cc * usb_endpoint.cc * usb_interface.cc Bug: 854831 Change-Id: Ie67533ece27f1c944b0e9186d01a61219a30f805 Reviewed-on: https://chromium-review.googlesource.com/1183789 Commit-Queue: Ovidio Henriquez <odejesush@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#586930} 29 August 2018, 00:04:53 UTC
2c03d31 Clip filter effects at the stacking context level. Much like mask images. This is the easy fix, for now. We need to override the ASR clips with Nothing() because we don't really want children of this display item to get the parent filter applied. It's not only redundant, but also may be incorrect if the mask image is not opaque for example (maybe WR should prevent that?). This was caught by layout/reftests/w3c-css/submitted/masking/mask-opacity-1a.html Differential Revision: https://phabricator.services.mozilla.com/D4351 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1459065 gecko-commit: ccf47d95dc9b3b9bd08dec0b0123480cfe4a18ca gecko-integration-branch: autoland gecko-reviewers: mstange 28 August 2018, 22:43:40 UTC
a76462c [wdspec] Add basic tests for "Get Element rect". bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1486456 gecko-commit: 4c623a756c06017d341d956ce5a8633baf3f7fc8 gecko-integration-branch: mozilla-inbound gecko-reviewers: ato 28 August 2018, 22:20:22 UTC
0f5d43a Merge pull request #12729 from Loirooriol/css-shorthand-initial Test that important flags are checked when serializing shorthand with "initial" values 28 August 2018, 22:03:40 UTC
3dae97c Add WPT serialization tests for wasm modules These WPT tests are based on similar tests in wpt/html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/ This also fixes some test failures for the SharedArrayBuffer tests. Bug: chromium:798572 Change-Id: I50b0edbebe4e97f5358513d248657d2831f48201 Reviewed-on: https://chromium-review.googlesource.com/1175490 Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#586480} 28 August 2018, 20:50:49 UTC
acf0ab1 Test that important flags are checked when serializing shorthand with "initial" values See https://bugs.webkit.org/show_bug.cgi?id=188984 28 August 2018, 20:33:07 UTC
back to top