Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
sort by:
Revision Author Date Message Commit Date
9454b8e Geoffrey Sneddon 27 August 2018, 16:01:41 UTC Fix #12578: make SeleniumExecutor/WebDriverExecutor use the right size for reftests 14 November 2018, 11:37:48 UTC
beb9940 James Graham 25 July 2018, 16:45:57 UTC Add support for fuzzy matching in reftests. 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). 14 November 2018, 11:37:48 UTC
59fba01 Boris Chiou 14 November 2018, 05:05:19 UTC Support keywords [x|y|z] on rotate. Update the parser and the serialization to support the keywords, [x|y|z]. Differential Revision: https://phabricator.services.mozilla.com/D11531 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1504327 gecko-commit: 3bc1fa72e7ebea23e81332aec81ed03f2fdf1cfc gecko-integration-branch: autoland gecko-reviewers: emilio 14 November 2018, 10:04:51 UTC
0e1c725 Harald Alvestrand 14 November 2018, 05:21:32 UTC Merge pull request #13784 from youennf/move-getDisplayMedia-to-MediaDevices Move getDisplayMedia to MediaDevices 14 November 2018, 05:21:32 UTC
e1a59fb Stephen Chenney 14 November 2018, 04:28:53 UTC Fix background image painting of very small images The background image fast path painting rounds the image src rect to integer sizes assuming sprite maps and/or reasonably large images. When a very small image is used scaled up to a large size (such as constant color images scaled up to form progress bars by animating background size) the src rect may be 1 x [small number] which gets rounded to zero size. This patch changes the code to detect this situation and not round in such cases. It's worth recording that an alternate approach is to detect when the rounding results in a significant change in src rect and always switch to unrounded in that case. But it would be more expensive for a relatively uncommon case. R=fmalita BUG=904042 Change-Id: I24657a5d087c0dda0fd8a5e3c3d08e1e4eb02473 Reviewed-on: https://chromium-review.googlesource.com/c/1334291 Reviewed-by: Florin Malita <fmalita@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#607901} 14 November 2018, 04:34:41 UTC
53ef64d François Beaufort 14 November 2018, 00:48:46 UTC [Picture-in-Picture] Move mediastream test to wpt. Change-Id: I6edc955ecd0d7f821d642bab0f66a6f25882c098 Reviewed-on: https://chromium-review.googlesource.com/c/1329141 Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#607837} 14 November 2018, 01:03:29 UTC
7201104 Steve Anton 13 November 2018, 19:51:17 UTC Implement RTCQuicStream.write() Bug: 874296 Change-Id: I1786acb3b64fa0450e76fe27300c178081d1e191 Reviewed-on: https://chromium-review.googlesource.com/c/1285528 Commit-Queue: Steve Anton <steveanton@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#607708} 13 November 2018, 20:01:29 UTC
ef5a7d3 François Beaufort 13 November 2018, 18:24:26 UTC [Picture-in-Picture] Fix shadow dom crash when exiting PiP. This CL fixes a tab crash that occurs when calling document.exitPictureInPicture() if a video in a shadow DOM is already in Picture-in-Picture. Bug: 904828 Change-Id: I6aed0fa43dd0af1406d4349509101d423f622d96 Reviewed-on: https://chromium-review.googlesource.com/c/1333769 Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#607658} 13 November 2018, 18:36:36 UTC
4cf6f84 Fredrik Söderquist 13 November 2018, 17:27:30 UTC Fixes and tweaks to wpt/css/filter-effects/ filter-contrast-003.html Adjust the color from #400000 to #3f0000, since (0x40 / 255) is just over 0.25 and can after filtering and rounding end up above 0. (0x3f / 255) on the other hand is just below 0.25 and the result will be clamped to zero. filter-external-001-test.html filter-external-002-test.html Change the hue-rotate parameter in the external file from 120 to 150. Move the file to support/ and remove lint entry. Make both filters operate in sRGB to make computing the reference easier. Use rgb(...) notation with percentage values in reference. fecolormatrix-type.html Add color-interpolation-filters=sRGB to the filter to make it easier to reason about what the result should be. Use rgba(...) notation in the ref using percentage notation. filters-test-brightness-003.html Add 'filter: brightness(0)' before 'filter: brightness()' to properly test if the "no argument" notation is considered valid by the parser. filter-grayscale-001.html filter-grayscale-002.html filter-grayscale-003.html filter-grayscale-004.html filter-grayscale-005.html Remove the " (and not blue)" text from the reference and update the 001,004 and 005 tests accordingly. css-filters-animation-saturate.html Interpolate the argument from 4900% rather than 5000% to end at the ref's 2500% (25). css-filters-animation-hue-rotate.html Sample the animation at .5 to match the expectation. css-filters-animation-drop-shadow.html Use explicit rgba(...) in the ref rather than the keyword 'gray'. We're interpolating the color of the drop-shadow from 'black' (rgba(0, 0, 0, 1)) to 'transparent' (rgba(0, 0, 0, 0)) here, so it's better and more accurate to describe the color as "semi-transparent black" (rgba(0, 0, 0, 0.5)). css-filters-animation-combined-001.html Initial value for animation for 'opacity(...)' is '1' - not zero. Change test to interpolate from 0 -> 1 (rather than 1 -> 1) Bug: 903383 Change-Id: I4d0113989414616494b98c22fbac817f007cd762 Reviewed-on: https://chromium-review.googlesource.com/c/1333816 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#607628} 13 November 2018, 17:38:14 UTC
645c0e8 Anne van Kesteren 13 November 2018, 17:14:33 UTC Fetch: Access-Control-Expose-Headers parsing See https://github.com/whatwg/fetch/issues/814 for context. 13 November 2018, 17:14:33 UTC
43b98d2 Ms2ger 13 November 2018, 17:08:29 UTC Python 3: Fix test_set_cookie. (#13623) 13 November 2018, 17:08:29 UTC
d499687 Hiroshige Hayashizaki 09 November 2018, 15:25:45 UTC Add redirected cases to CSP/import tests in wpt/worklets Also this CL replaces some of empty-worklet-script.js usage in CSP tests with empty-worklet-script-with-cors-header.js to make sure worklets are rejected due to CSP, not CORS. Change-Id: Ie463d206254c4c6728a79dae0ad79e4f7e333b92 Reviewed-on: https://chromium-review.googlesource.com/c/1312146 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#606846} 13 November 2018, 15:54:10 UTC
7ecc4ec Chris Lilley 13 November 2018, 15:40:52 UTC Merge pull request #14032 from ewilligers/svg-text-inheritance SVG Text: inheritance, initial values 13 November 2018, 15:40:52 UTC
0d5c1ad Chris Lilley 13 November 2018, 15:38:37 UTC Merge pull request #14031 from ewilligers/painting-inheritance SVG Painting: inheritance and initial values 13 November 2018, 15:38:37 UTC
414fbd5 Nils Ohlmeier 13 November 2018, 00:03:38 UTC disable Firefox WebRTC ICE logging to reduce log size 13 November 2018, 14:38:50 UTC
bbaede3 Eric Willigers 13 November 2018, 12:11:01 UTC SVG Geometry Properties - parsing (#13951) The properties cx cy r rx ry x y have the specified initial values, grammar and inheritance behavior. https://svgwg.org/svg2-draft/geometry.html Radii cannot be negative. Unitless lengths are not permitted. 13 November 2018, 12:11:01 UTC
5124d93 Eric Willigers 13 November 2018, 11:11:55 UTC SVG Text: inheritance, initial values Test that SVG text properties inherit according to spec. Test that they have the expected initial values. https://svgwg.org/svg2-draft/text.html 13 November 2018, 11:19:15 UTC
fde96a6 Kent Tamura 12 November 2018, 08:02:25 UTC Preparation of moving LayoutTests to web_tests. * layout_test_content_browser_client.cc: Pass --tests-in-blink flag to a renderer process. GetWebTestsFilePath() in blink_test_helpers.cc needs this flag. * LayoutTests/editing/assert_selection.html * LayoutTests/editing/assert_selection.js * LayoutTests/editing/execCommand/insert-paragraph-into-table-expected.txt Drop 'LayoutTests/' part from error description * LayoutTests/external/wpt/bluetooth/resources/bluetooth-helpers.js * LayoutTests/external/wpt/webusb/resources/usb-helpers.js Support web_tests/ as well as LayoutTests/ * LayoutTests/fast/js/exception-line-number-expected.txt * LayoutTests/fast/js/script-tests/exception-line-number.js Drop 'LayoutTests/' part from error description Bug: 843412 Change-Id: I817b40bb2e7edf0216a32d9f3a3e2320e4b6956a Reviewed-on: https://chromium-review.googlesource.com/c/1329811 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#607165} 13 November 2018, 11:14:36 UTC
2281bfa Christian Biesinger 12 November 2018, 22:05:41 UTC [css-flexbox] ChildIntrinsicLogicalWidth should use fit-content, not max-content This function needs to match the actual sizing we use. But, since this is the cross-axis size, we use fit-content: https://drafts.csswg.org/css-flexbox/#algo-cross-item See LayoutBox::SizesLogicalWidthToFitContent and LayoutBox::ComputeLogicalWidthUsing for where we do that fit-content sizing; this code makes us match the ComputeLogicalWidthUsing calculation. This bug is currently somewhat hard to trigger because it requires a combination of all of: - flex-wrap: wrap - flex-direction: column - More than one flex line - Not using align-items: flex-start or align-content: flex-start - No explicit width on the flex item - The max-content width needs to be larger than the width of flexbox The reason this does not matter in other cases is because we only use this function to set FlexLine::cross_axis_extent, which we overwrite in AlignFlexLines if we only have one line. And if we do have more than one line, we only use this value for aligning items and lines, so it only matters if we don't use flex-start alignment. This bug will be much easier to trigger once bug 599828 is fixed (there are at least two real-world sites that are affected by this once that bug is fixed) Bug: 876749 Change-Id: I673026bedfaf0e4c4a25830ef686b200ec8f54a1 Reviewed-on: https://chromium-review.googlesource.com/c/1327746 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#607342} 13 November 2018, 11:12:49 UTC
9a723ed Javier Fernandez 13 November 2018, 10:50:56 UTC [css-text] Skip trailing spaces for pre-wrap even if word can be broken According to the specs, preserved white-spaces should hang, or visually collapse, when white-space is set to pre-wrap; even if word-break allows breaing the word at any point. https://www.w3.org/TR/css-text-3/#line-break-details Bug: 768363 Change-Id: I7ab356ed6f789ecef087ff469ad97c50e7af49be Reviewed-on: https://chromium-review.googlesource.com/c/1318694 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#607550} 13 November 2018, 11:00:48 UTC
1794ecf Eric Willigers 13 November 2018, 10:50:01 UTC SVG Painting: inheritance and initial values Painting properties inherit, and have the expected initial values. https://svgwg.org/svg2-draft/painting.html 13 November 2018, 10:58:29 UTC
683ea00 Philip Jägenstedt 13 November 2018, 10:30:39 UTC Update infrastructure/metadata/ to match Chrome and Firefox results 13 November 2018, 10:41:18 UTC
29a37f9 Lan Wei 09 November 2018, 17:32:25 UTC Add action_sequence in testdriver After we expose test_driver.Actions API to web users, we add their implementation in our testdriver file, and fix the wpt tests of Actions API. Bug: 893480 Change-Id: Ib02c0223208eeb2cc30c2ca35b98d5fc938baa2c Reviewed-on: https://chromium-review.googlesource.com/c/1289119 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#606882} 13 November 2018, 10:41:18 UTC
3571d11 Hiroki Nakagawa 13 November 2018, 04:59:29 UTC ServiceWorker: Deflake update-with-script-type.https.html To sheriff: Please re-disable the test if it's still flaky. In this test file, some tests start re-registering the second service worker before the first service worker gets activated. In my theory, this sometimes squashes the second registration job into the first registration job, and results in test flakiness. This CL makes sure the second register runs after the first service worker gets activated. Note that it would be the correct behavior that the second registration job isn't squashed when the script type is changed. There is a spec issue about this: https://github.com/w3c/ServiceWorker/issues/1358 Bug: 901317 Change-Id: I7ce379071a35ef9aeb98e4492d651ee6fc4714ec Reviewed-on: https://chromium-review.googlesource.com/c/1328546 Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#607494} 13 November 2018, 10:08:31 UTC
5abc7ea Asami Doi 01 November 2018, 10:54:32 UTC ServiceWorker: Add new WPT tests to make sure to update a registration with different script type and identical script content. These tests check that a registration is updated correctly with different script type. At first Service Worker is registered as classic script type, then it is re-registered as module script type, and vice versa. A main script is identical. Bug: 824647 Change-Id: I2a3f87da1013f84c6e9495f362899dfe6ab97b45 Reviewed-on: https://chromium-review.googlesource.com/c/1298822 Commit-Queue: Asami Doi <asamidoi@google.com> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#604551} 13 November 2018, 10:08:31 UTC
823de78 Mike West 13 November 2018, 09:31:48 UTC Enable Feature Policy control over setting `document.domain`. Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/Ff6Ywg5vnh4/VbDH4X6wBQAJ Explainer: https://github.com/WICG/feature-policy/issues/241 Spec PR: https://github.com/whatwg/html/pull/4170 Bug: 904351 Change-Id: I14c0c3c871a01017f9c2bcbe8ed41c7b26782e71 Reviewed-on: https://chromium-review.googlesource.com/c/1329791 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#607530} 13 November 2018, 09:41:44 UTC
e1bde44 Mason Freed 13 November 2018, 02:28:01 UTC Re-plumb backdrop-filter through blink-gen-property-trees With this CL, backdrop-filter will continue to work when the --enable-blink-gen-property-trees flag is enabled. Behavior should be identical to behavior without the flag. Also, I added a number of layout/WPT tests for backdrop-filter, some of which currently pass, and some of which need fixing. The ones that need fixing have been added to TestExpectations. These new tests should reproduce (at least) these issues: - https://crbug.com/314867 - respecting isolation - https://crbug.com/525099 - respecting isolation - https://crbug.com/547937 - border radius - https://crbug.com/524689 - filter plus backdrop-filter - https://crbug.com/745012 - boundary effect problems I also moved the existing tests out of external/wpt/css/css-filter into external/wpt/css/filter-effects, where they really should be, now that filter-effects is being pulled into the tree. Bug: 497522,314867,525099,547937,524689,745012 Change-Id: I2be33fbc0e17dec2cd138f9796971fb4a9a57216 Reviewed-on: https://chromium-review.googlesource.com/c/1316661 Commit-Queue: Mason Freed <masonfreed@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#607447} 13 November 2018, 02:39:01 UTC
89188af Andreas Tolfsen 08 November 2018, 16:21:59 UTC webdriver: add stress tests for window manipulation Depends on D8410 Differential Revision: https://phabricator.services.mozilla.com/D8411 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1492499 gecko-commit: 8490a7301d9270bd4cf4e25ac871136152f172ab gecko-integration-branch: autoland gecko-reviewers: automatedtester 12 November 2018, 18:22:33 UTC
7137e11 Andreas Tolfsen 08 November 2018, 16:21:57 UTC webdriver: take 22px window border into account on maximizing On some systems and window managers, such as macOS and when X11 forwarding an application across systems, there exists a 22px window border that we cannot detect or do anything about. As this test is to verify that the width/height changed beyond 800x600, this assertion change should make the tests pass on more configurations. Depends on D8409 Differential Revision: https://phabricator.services.mozilla.com/D8410 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1492499 gecko-commit: 83ee1c23d31a360c315487d25bc648bc80404682 gecko-integration-branch: autoland gecko-reviewers: automatedtester, whimboo 12 November 2018, 18:22:33 UTC
6914e48 Andreas Tolfsen 07 November 2018, 17:59:14 UTC webdriver: test scroll behaviour on partially visible elements Partially visible elements should according to WebDriver not be scrolled into view. Drivers first run the in-view centre point algorithm to determine if any portion of the targetted element is in view, and if it is not, the element is scrolled into view. As little as a 1 CSS pixel is sufficient for the element to deemed in view. Implementations have had problems with deeming elements out of view when a single pixel border has in fact been in view due to faulty rounding of the target point, which is why we test a range from 10 to 1 pixels. Depends on D10821 Differential Revision: https://phabricator.services.mozilla.com/D10822 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1493115 gecko-commit: d1a6af0172d9535f91063526c654f7719dc55440 gecko-integration-branch: central gecko-reviewers: whimboo 12 November 2018, 18:22:01 UTC
d7c7556 moz-wptsync-bot 07 November 2018, 17:42:16 UTC webdriver: move center_point into helpers Differential Revision: https://phabricator.services.mozilla.com/D10821 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1493115 gecko-commit: d3bf4055a5196a5cf0afb670ca6f6a116fee22bb gecko-integration-branch: central gecko-reviewers: whimboo 12 November 2018, 18:22:01 UTC
42392b1 Nico Grunbaum 06 November 2018, 04:55:43 UTC Correct WebRTC getStats WPT to wait for remote stats before comparing If care is not taken to wait for remote stats on senders and receivers, then the contents of the stats reports will not be stable. Waiting for this stability should fix our intermittent failures checking that RTCRtpSender/Receiver.getStats() returns the same dictionaries that RTCPeerConnection.getStats(sender/receiver.track) does. Differential Revision: https://phabricator.services.mozilla.com/D5804 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1457129 gecko-commit: 0874b793fc046bf31ca80c673d5dfa0bb38ea343 gecko-integration-branch: autoland gecko-reviewers: jib 12 November 2018, 18:21:32 UTC
b310ad5 Wes Kocher 12 November 2018, 10:33:54 UTC Fix up two other instances of ParseError not passing in metadata Depends on D11575 Differential Revision: https://phabricator.services.mozilla.com/D11576 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1506410 gecko-commit: 702485851935a8b3efb62b5efd3b82543b5167a4 gecko-integration-branch: autoland gecko-reviewers: jgraham 12 November 2018, 17:32:33 UTC
ef4c0dc Wes Kocher 12 November 2018, 10:19:27 UTC Make sure wptmanifest's ParseError prints out filename and line number when called Differential Revision: https://phabricator.services.mozilla.com/D11575 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1506410 gecko-commit: b6509b248af41520402cc18a86fa408af9c8b95d gecko-integration-branch: autoland gecko-reviewers: jgraham 12 November 2018, 17:32:33 UTC
860091d Daniel Vogelheim 12 November 2018, 15:31:22 UTC HTMLScriptElement text attributes modified to accept TrustedTypes HTMLScriptElement::text() and setText() functions modified to accept TrustedScript as an argument. Added HTMLScriptElement::innerText and HTMLScriptElement:textContent attributes to override existing implementations in HTMLElement and Node, and to accept TrustedScript. Changed HTMLElement::innerText and Node::textContent .idl definitions and adjusted setters and getters to accept TrustedScript. Bug: 739170 Change-Id: I63da5714ffac328c6ae2f76e5da58c05f44a1cbf Reviewed-on: https://chromium-review.googlesource.com/c/1178046 Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#607232} 12 November 2018, 15:37:01 UTC
d0c94e6 qiuzhong 12 November 2018, 03:50:59 UTC Read and write files in binary mode Read and write files in binary mode so the unit tests can pass in Python3 environment. 12 November 2018, 13:53:56 UTC
dfbb0fd qiuzhong 12 November 2018, 02:46:51 UTC Update the unit tests * Fix the import error * Improve the code style 12 November 2018, 13:53:56 UTC
2225031 qiuzhong 09 November 2018, 11:18:34 UTC Add unit tests for wrapper handlers in tools/serve Add unit tests for all kinds of wrapper handlers in tools/serve/serve.py. See #12452 12 November 2018, 13:53:56 UTC
0d4f539 Morten Stenshorne 12 November 2018, 13:41:52 UTC Set orphans and widows to 1 in new multicol test. The test left orphans / widows at their initial value (2), but did assume that we could freely break wherever we wanted. Blink honors orphans and widows requirements inside multicol containers, so set them to 1, to get the behavior that the test expects. Bug: 904263 Change-Id: Ia138da5c65b1c5da450441f38e033320bc983a94 Reviewed-on: https://chromium-review.googlesource.com/c/1331389 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#607211} 12 November 2018, 13:47:10 UTC
2f868fa Antoine Quint 12 November 2018, 10:41:51 UTC Typo: "opoacity" should be "opacity" (#14018) 12 November 2018, 10:41:51 UTC
315b16b Joshua Bell 12 November 2018, 10:37:07 UTC Encoding: fix UTF-32 tests Closes #10588. 12 November 2018, 10:37:07 UTC
7190721 Boris Chiou 09 November 2018, 22:21:52 UTC Percentage values of translate are serialized as percent for computed values. Basically, we rewrite the type of generics::transform::Translate and its ToCss to match the spec. Besides, we always serialize Translate by servo, so we could drop a lot of duplicated code. Differential Revision: https://phabricator.services.mozilla.com/D11206 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1505156 gecko-commit: 14e4e5920241b77cea5e6881d782691105728723 gecko-integration-branch: autoland gecko-reviewers: emilio 12 November 2018, 10:34:14 UTC
6aeb68e Anne van Kesteren 12 November 2018, 09:27:06 UTC MIME types: test 0x0B, 0x0C, and newlines For https://github.com/whatwg/mimesniff/pull/90. 12 November 2018, 09:27:06 UTC
67fe8ce Florian Rivoal 12 November 2018, 05:32:16 UTC Merge pull request #13336 from frivoal/text-2883 [css-text] Advance width of a tab must be at least 0.5ch 12 November 2018, 05:32:16 UTC
bfa6d94 Mark Roberts 08 November 2018, 05:55:00 UTC Fix typo in RTCPeerConnection-setLocalDescription-offer.html `offer2` is accidentally shadowed. 12 November 2018, 03:05:50 UTC
fc1a5b7 jimevans 11 November 2018, 23:14:25 UTC Remove ES6 object matching shorthand notation from WebDriver tests (#14015) This change is to allow older user agents that do not support ES6 constructs to run the WebDriver tests. 11 November 2018, 23:14:25 UTC
926d722 CYBAI 11 November 2018, 06:13:31 UTC Update to new ServiceWorker spec link 11 November 2018, 08:36:47 UTC
abc39b8 Emilio Cobos Álvarez 09 November 2018, 21:08:59 UTC Make images without alt generate a replaced box regardless of src. Behavior-wise this only removes the HasAttr(src) check, and adds the IsEmpty() check to the alt attribute value, since this function is only called for <img> and <input>. But it also cleans up a bit. Differential Revision: https://phabricator.services.mozilla.com/D11194 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1196668 gecko-commit: c8f6772dab9afd70d0d5015f653d6df9a9e6bee3 gecko-integration-branch: mozilla-inbound gecko-reviewers: bz 10 November 2018, 21:48:37 UTC
f631930 Ting-Yu Lin 10 November 2018, 01:24:47 UTC Part 2 - Do not carry block-end margin out of ColumnSetFrame. Also, remove the unused NS_BLOCK_MARGIN_ROOT flag set on nsColumnSetFrame. Differential Revision: https://phabricator.services.mozilla.com/D8783 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1497990 gecko-commit: 730a64fdde3e31df33d918d2c4221f598e064d44 gecko-integration-branch: autoland gecko-reviewers: dbaron 10 November 2018, 11:57:25 UTC
a0610cf Sandra Sun 09 November 2018, 23:19:39 UTC Snap at ScrollIntoView. According to the spec, https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-386154394 scrollIntoView should 1) Always snap to the target element's snap alignment, and 2) All the affected scrollers should also land on a snap position if one exists. This patch does part 2). Before a scrollable_area is added to the smoothScrollSequencer with its new scroll_offset, we will check if it has a valid snap offset around, and update the final offset accordingly. We'll implement part 1) in a separate patch. Bug: 842317 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ica22134ed0b1f9d36f5a017c8dd0be54e907dd3d Reviewed-on: https://chromium-review.googlesource.com/c/1188746 Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Cr-Commit-Position: refs/heads/master@{#607019} 09 November 2018, 23:30:06 UTC
4f27740 Mike Pennisi 09 November 2018, 21:56:48 UTC [wptserve] Correct typos 09 November 2018, 23:00:46 UTC
d7a9bb5 autofoolip 09 November 2018, 22:55:41 UTC Update interfaces/css-transitions.idl (#13997) Source: https://github.com/tidoust/reffy-reports/blob/83bbd56/whatwg/idl/css-transitions.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/452744285 09 November 2018, 22:55:41 UTC
a27659a Tab Atkins Jr 09 November 2018, 21:54:22 UTC Merge pull request #13977 from ewilligers/grid-template-areas-serialization-2 grid-template-areas serialization 09 November 2018, 21:54:22 UTC
9902fba Douglas Creager 09 November 2018, 20:58:36 UTC NEL: Generate reports in HTTPNetworkTransaction Piece by piece, we are moving the Reporting and NEL processing code from URLRequest and friends into HTTPNetworkTransaction, to make sure that we produce reports for network requests as defined by the spec. This patch moves the generation of the actual NEL reports, and includes some new WPT test cases that verify that we create reports correctly for redirects and cached responses. TBR=msramek@chromium.org Bug: 895823 Change-Id: Ie8e17a2a2b3571a7cdfd39057da486f5ad2c9f6f Reviewed-on: https://chromium-review.googlesource.com/c/1318169 Commit-Queue: Douglas Creager <dcreager@chromium.org> Reviewed-by: Misha Efimov <mef@chromium.org> Cr-Commit-Position: refs/heads/master@{#606958} 09 November 2018, 21:13:48 UTC
7d985c2 Dominic Farolino 26 October 2018, 03:11:12 UTC Redo tests 09 November 2018, 18:57:46 UTC
7c568fd Ahilya Sinha 27 September 2018, 11:10:41 UTC browser.py code cleanup Some code cleanup that was recommended in https://github.com/web-platform-tests/wpt/pull/13185 09 November 2018, 17:21:48 UTC
726725b James Graham 24 October 2018, 09:54:57 UTC Add a wpt create command wpt create makes a file with the required elements for a test, and optionally opens it in an editor. 09 November 2018, 17:19:58 UTC
378b79a Joshua Bell 09 November 2018, 17:06:01 UTC webkitRelativePath preserves common ancestors (#13988) Drop requirement that webkitRelativePath only provides the shortest common ancestor, which matches behavior in Edge/Safari/Firefox, and soon Chrome. Spec change: https://github.com/WICG/entries-api/commit/e6b848f4dcd17e25c2bab2a70e38ee9950687d12 Tracking issue: WICG/entries-api#18 09 November 2018, 17:06:01 UTC
0550770 Guido Urdaneta 09 November 2018, 16:07:29 UTC Wire the resizeMode property to the constraints parsing mechanism. This CL adds resizeMode support for MediaStreamTrack.getConstraints() and marks resizeMode as a supported constrainable property. Support for getUserMedia(), applyConstraints() and getCapabilities() will be added in follow-up CLs in this series. Intent to Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/V2srjdzRCXE Bug: 854980 Change-Id: Ia23b8119768ab67ab498f0f8e2267aeb388f9fc3 Reviewed-on: https://chromium-review.googlesource.com/c/1309749 Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#606856} 09 November 2018, 16:18:08 UTC
bc002a5 James Graham 09 November 2018, 14:44:16 UTC Fixup logging in stability checks 09 November 2018, 15:50:11 UTC
4176e9e Luke Bjerring 09 November 2018, 14:41:38 UTC Count partial mixins as tested deps (#13878) 09 November 2018, 14:41:38 UTC
47f0061 James Graham 17 October 2018, 16:12:07 UTC Setup logging earlier in the wpt run startup. Curerntly we wait until we're setting up wptrunner kwargs to create the logger. But that's pretty silly; we should set up the logger first thing and then use it consistently to log during the setup phase. 09 November 2018, 10:29:54 UTC
80d76f8 autofoolip 09 November 2018, 10:00:07 UTC Update interfaces/selection-api.idl (#14000) Source: https://github.com/tidoust/reffy-reports/blob/83bbd56/whatwg/idl/selection-api.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/452744285 09 November 2018, 10:00:07 UTC
c506a34 autofoolip 09 November 2018, 09:59:46 UTC Update interfaces/webrtc.idl (#14001) Source: https://github.com/tidoust/reffy-reports/blob/83bbd56/whatwg/idl/webrtc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/452744285 09 November 2018, 09:59:46 UTC
7d90704 John Chen 09 November 2018, 05:15:35 UTC Do not send old capabilities to ChromeDriver The configuration for Chrome currently sends 'platform' and 'version' capabilities to ChromeDriver. These capabilities are non-standard and unnecessary, and will cause errors when ChromeDriver becomes more standard compliant. 09 November 2018, 09:29:53 UTC
eed621b Anne van Kesteren 09 November 2018, 08:15:37 UTC Fetch: CORS and request's Content-Type header For https://github.com/whatwg/fetch/pull/829. 09 November 2018, 08:15:37 UTC
d147908 Emilio Cobos Álvarez 09 November 2018, 05:14:34 UTC Implement overflow-wrap: anywhere. Per https://github.com/w3c/csswg-drafts/issues/2682 Differential Revision: https://phabricator.services.mozilla.com/D11328 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1505786 gecko-commit: 9a315872bd6d11ac42871b083961a00fa53ee753 gecko-integration-branch: autoland gecko-reviewers: xidorn, jfkthame 09 November 2018, 06:43:07 UTC
a996d20 Ting-Yu Lin 09 November 2018, 01:01:35 UTC Part 5 - Fix anonymous -moz-column-span-wrapper block's style is overridden after restyling. The major change in this patch is ::-moz-column-span-wrapper blocks are no longer linked into the continuation chains when they're created in CreateColumnSpanSiblings(). We can do that because ::-moz-column-span-wrapper is an non-inheriting anon box, which doesn't need to be restyled. This prevents RestyleManager::ProcessPostTraversal or nsIFrame::UpdateStyleOfOwnedChildFrame, which set the same style on all continuations of the frame they are working with, from overriding the ::-moz-column-span-wrapper style. GetNextContinuationWithSameStyle was deleted in bug 1447367. Delete the comment in nsInlineFrame::UpdateStyleOfOwnedAnonBoxesForIBSplit() to avoid confusion. This patch also adds another condition to reframe the multi-column container in MaybeRecreateContainerForFrameRemoval(). That condition is when an element has a "column-span:all" descendant, i.e. the element's frame has "column-span:all" siblings (which is created by CreateColumnSpanSiblings). The added test multicol-span-all-dynamic-remove-006.html will fail without this patch. Depends on D5212 Differential Revision: https://phabricator.services.mozilla.com/D9988 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1421105 gecko-commit: 5d474106adceacb64ca5f987fa75f75f2ed6feb6 gecko-integration-branch: autoland gecko-reviewers: bzbarsky, emilio 09 November 2018, 05:57:09 UTC
e2d7a95 Ting-Yu Lin 09 November 2018, 01:01:34 UTC Part 3 - Support dynamically adding or removing elements under multi-column subtree. Depends on D5209 Differential Revision: https://phabricator.services.mozilla.com/D5210 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1421105 gecko-commit: 2610d4f32f9143813a00a326fee541f7db078f7f gecko-integration-branch: autoland gecko-reviewers: bzbarsky, dbaron 09 November 2018, 05:57:09 UTC
3cd6090 Kent Tamura 09 November 2018, 03:59:29 UTC html: Fix a sanitization issue of type-change-state.html type-change-state.html assumed sanitized value for " foo\rbar " was fixed per a input type, and it was specified by 'sanitizedValue' field. However, it depends on the previous type. For example, the new input types of the following A and B are same, initial value setter arguments are same, but sanitized values of A and B should be different due to the sanitizer difference between 'hidden' and 'url': A) input.type = "hidden"; input.value = " foo\rbar "; // input.value is " foo\rbar " input.type = "text"; // input.value is " foobar ". B) input.type = "url"; input.value = " foo\rbar "; // input.value is "foobar" input.type = "text"; // input.value is "foobar". This CL fixes this issue by replacing 'sanitizedValue' field with 'sanitizer' field, which specifies a simple sanitizer implementation. This fixes five test cases, which have failed with all major browsers. Change-Id: I1b5f75e610138b1d117e93723471427ee655c300 Reviewed-on: https://chromium-review.googlesource.com/c/1326203 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#606730} 09 November 2018, 04:09:33 UTC
d5be80a Yutaka Hirano 09 November 2018, 01:01:17 UTC [media] Treat cross-origin redirect as TAINTED only for no-cors requests With https://crrev.com/a9cbaa7a40e2b2723cfc2f266c42f4980038a949, WebMediaPlayer blindly treats a resource experiencing cross-origin redirects as TAINTED. In fact, it should be treated as TAINTED only when its request mode is "no-cors". The added tests are provided by hongchan@chromium.org. Bug: 899745, 901383 Change-Id: Idb66407552085b053818f3e4a9d8d5ff3ddeaf45 Reviewed-on: https://chromium-review.googlesource.com/c/1325281 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Reviewed-by: Fredrik Hubinette <hubbe@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#606681} 09 November 2018, 01:11:14 UTC
a516e7e Max Rebuschatis 08 November 2018, 23:19:29 UTC Reland "Make XR FrameData and Environment mojo associated" This is a reland of 126a1168e3bcffb43c706822b3aa28695840310f The fix in this change addresses compile errors on the Oculus platform. TBR=dcheng@chromium.org dcheng@chromium.org: please review, though there are no new changes to vr_service.mojom Original change's description: > Make XR FrameData and Environment mojo associated > > The XRFrameDataProvider now returns an associated > XREnvironmentDataProvider interface so that the > two share callback queues and thus allow strict > ordering of the two interfaces. This is critical > for frame synchronization between frames and the > associated environment data. > > Note: We can't just mark the interfaceptrs for > XRFrameDataProvider and > XREnvironmentIntegrationProvider as associated > in the XRSession struct. XRDevice implementations > mostly live on separate threads from the > XRFrameDataProviders, so we'd have extra thread > hopping. For the VR headsets we explicitly live > off the main thread to avoid latency, and because > we do some work that may block the thread the > XRFrameDataProvider lives on (for example waiting > for vsync, or submitting frames to headset APIs). > > Bug: 867057, 876135, 843376 > Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30 > Reviewed-on: https://chromium-review.googlesource.com/c/1171794 > Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Bill Orr <billorr@chromium.org> > Reviewed-by: Klaus Weidner <klausw@chromium.org> > Cr-Commit-Position: refs/heads/master@{#605545} Bug: 867057, 876135, 843376 Change-Id: If76578ebabbb40d03a21f6f557c5d4c27f69fc38 Reviewed-on: https://chromium-review.googlesource.com/c/1324089 Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org> Reviewed-by: Bill Orr <billorr@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#606643} 08 November 2018, 23:25:17 UTC
a337ff8 Karl Tomlinson 05 November 2018, 23:29:57 UTC test 3 events of the same type at the same time Depends on D10860 Differential Revision: https://phabricator.services.mozilla.com/D10861 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503950 gecko-commit: bf705d04c328085c490e5a9f111b9143123b3cc9 gecko-integration-branch: autoland gecko-reviewers: padenot 08 November 2018, 22:47:43 UTC
b207ce6 Emilio Cobos Álvarez 08 November 2018, 16:59:34 UTC Allow ::slotted()::placeholder. Differential Revision: https://phabricator.services.mozilla.com/D11132 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1505213 gecko-commit: 8735038d615f99a6a9fe4fa44d26be3b6b6bb727 gecko-integration-branch: autoland gecko-reviewers: heycam 08 November 2018, 20:44:48 UTC
cc3cc47 aestes 08 November 2018, 20:25:33 UTC Add aestes as a payment-request/ suggested reviewer. (#13987) 08 November 2018, 20:25:33 UTC
6e6b837 pyup.io bot 08 November 2018, 18:38:43 UTC Update requests to 2.20.1 (#13986) 08 November 2018, 18:38:43 UTC
577284e Andreas Tolfsen 07 November 2018, 18:18:28 UTC webdriver: reduce amount of styling in element click interactability test The amount of CSS styling in this test is too damn high. Differential Revision: https://phabricator.services.mozilla.com/D10823 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1504485 gecko-commit: 534388d7e52d03862a0645737f8960ab404e8f35 gecko-integration-branch: autoland gecko-reviewers: whimboo 08 November 2018, 17:01:06 UTC
4477b9d François REMY 08 November 2018, 11:02:44 UTC The computed value of float with absolute positioning when there is no box should be "none" (#13958) https://github.com/w3c/csswg-drafts/issues/1436 08 November 2018, 11:02:44 UTC
b759b82 Dirk Schulze 08 November 2018, 05:08:09 UTC Merge pull request #13979 from ewilligers/filter-effects-reviewers [filter-effects] Add chrishtr as reviewer 08 November 2018, 05:08:09 UTC
603b17f Kent Tamura 08 November 2018, 03:17:07 UTC html: Fix an issue of type-change-state.html about selectionDirection="none" type-change-state.html contains assertions for the following operation in [1]: > ..., and set its selection direction to "none". However it had an issue that the assertions checked if input.selectionDirection was "none". According to [2], input.selectionDirection can be "forward" on specific platforms. > update the element's selection direction to the given direction, unless > the direction is "none" and the platform does not support that direction; > in that case, update the element's selection direction to "forward". [1] https://html.spec.whatwg.org/multipage/input.html#the-input-element:set-the-selection-direction [2] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#set-the-selection-direction Change-Id: Idc1a97fbb2036e351a788a1f758b3239308d8c71 Reviewed-on: https://chromium-review.googlesource.com/c/1322264 Reviewed-by: Rakina Zata Amni <rakina@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#606310} 08 November 2018, 03:27:08 UTC
d736af6 Boris Chiou 07 November 2018, 02:19:58 UTC Fix the default behavior of scale:<number>{1}. The current spec says: "If only the X value is given, the Y value defaults to the same value.", so we should update the behavior. Besides, we also update the serialization, so we serialization both specified and computed value by servo. We enable the preference for all the css-transforms, so some of them are passed now. Differential Revision: https://phabricator.services.mozilla.com/D10638 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1500107 gecko-commit: ffb8562ce45df606313c89723ed87bf015c3372e gecko-integration-branch: autoland gecko-reviewers: birtles 08 November 2018, 03:23:48 UTC
1ea8577 Eric Willigers 08 November 2018, 03:17:39 UTC [filter-effects] Add chrishtr as reviewer 08 November 2018, 03:17:39 UTC
da90a07 Eric Willigers 27 October 2018, 07:40:41 UTC grid-template-areas serialization strings in grid-template-areas are normalized, e.g. collapsing whitespace to a single space, and collapsing repeated periods ('.') to a single period. https://github.com/w3c/csswg-drafts/issues/3261#issuecomment-436828363 08 November 2018, 00:58:30 UTC
cd44958 L. David Baron 08 November 2018, 00:39:50 UTC Sync Mozilla CSS tests as of https://hg.mozilla.org/mozilla-central/rev/d87537833fcfd8d18f4d1c2782631c79c161a281 . (#13974) This contains a single change, from [bug 1500107](https://bugzilla.mozilla.org/show_bug.cgi?id=1500107), by @BorisChiou, already reviewed by @birtles. 08 November 2018, 00:39:50 UTC
c13b42a youennf 08 November 2018, 00:38:41 UTC Update replaceTrack after removeTrack tests (#13916) * Update replaceTrack after removeTrack tests 08 November 2018, 00:38:41 UTC
349d418 Adam Rice 07 November 2018, 21:15:21 UTC [streams] Add tests for aborting pipeTo() Add tests for aborting ReadableStream.prototype.pipeTo using an AbortSignal. Tests correspond to PR whatwg/streams#744. 07 November 2018, 21:15:21 UTC
8762072 Rayan Kanso 07 November 2018, 19:26:47 UTC [Background Fetch] Reject call to updateUI if event is inactive. Spec: https://wicg.github.io/background-fetch/#background-fetch-update-ui-event-update-ui Bug: 901909 Change-Id: Ia319cd03e41e65c5a6a1f5e61cde6f4ae7705a32 Reviewed-on: https://chromium-review.googlesource.com/c/1320330 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#606118} 07 November 2018, 19:36:58 UTC
920e3b1 Katie Dillon 06 November 2018, 23:35:13 UTC Window onerror is not triggered bug fix As pointed out in the bug, unhandled errors on worker threads were not properly being propagated for the parent thread to handle as the spec requires (https://html.spec.whatwg.org/multipage/workers.html#runtime-script-errors-2). This fix adds in the code to do that. Bug: 685303 Change-Id: Ie3e7ec03153a43efdc6e70b874d6b1a1d8ac35ef Reviewed-on: https://chromium-review.googlesource.com/c/1287208 Commit-Queue: Katie Dillon <kdillon@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#605857} 07 November 2018, 16:58:04 UTC
dea2771 Henrik Skupin 05 November 2018, 18:30:27 UTC [wdspec] Assert for expected screenshot dimensions. Depends on D10627 Differential Revision: https://phabricator.services.mozilla.com/D10628 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503804 gecko-commit: 076d32d1343fa0203bbf58209a45c73f2c878d97 gecko-integration-branch: autoland gecko-reviewers: ato 07 November 2018, 15:34:59 UTC
c783b96 Henrik Skupin 05 November 2018, 18:30:26 UTC [wdspec] Use shared assert_png() method in screenshot tests. Depends on D10626 Differential Revision: https://phabricator.services.mozilla.com/D10627 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503804 gecko-commit: 8ee95012eaf0271baf406be0f0b712198f9e01da gecko-integration-branch: autoland gecko-reviewers: ato 07 November 2018, 15:34:59 UTC
d30c8c0 Gijs Kruitbosch 01 November 2018, 08:40:41 UTC extend timeout on wpt tests because linux asan Differential Revision: https://phabricator.services.mozilla.com/D10396 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503624 gecko-commit: 29ebdc54d6bc82f8e5696f5129feffe2929460f3 gecko-integration-branch: autoland gecko-reviewers: jgraham 07 November 2018, 15:33:45 UTC
89692ea Žan Doberšek 07 November 2018, 15:32:50 UTC webkit: add support for the WPE port (#13863) WPE port is closely related to the GTK port, using the same WebDriver implementation as well as similar testing-purpose browser application. Much of the capabilities dictionary construction can thus be the same. 07 November 2018, 15:32:50 UTC
275904c jgraham 07 November 2018, 15:22:36 UTC Ensure that lone surrogates don't appear in wptreport json (#13828) Python will happily handle "string" data containing codepoints in the surrogate range. In the JSON output these are always escaped and appear as \uD800 or similar. That's pretty unfortunate for interop since other languages don't necessarily support such codepoints not representing a character in the unicode set in their normal string type. Although it's possible to clean this up on import it seems more reasonable to ensure that our primary interchange format is unicode-clean. Therefore this change starts escaping lone surrogates using the U+ notation so that \uD800 becomed U+D800. Because Python, this requires two implementations. In UCS4 Python we know that only lone surrogates should appear in string data; characters outside the BMP will be represented as a single internal character (*technically* this is untrue since someone may manually create a string containing a sequence of surrogates that happens to form a pair; we don't care about handling this case other than as two unpaired surrogates that happen to be adjacent). In UCS2 Python surrogates appear in the string data literally, so we need to check each time we encounter one whether it's a low surrogate followed by a high surrogate and not escape in that case. 07 November 2018, 15:22:36 UTC
1a7cb3d Luna Lu 07 November 2018, 15:10:29 UTC update wpt feature policy tests, making them long tests Bug: 829921 Change-Id: Ia2c70c62d4a4235b21996bbd185746080e1efa35 Reviewed-on: https://chromium-review.googlesource.com/c/1320010 Reviewed-by: Robert Ma <robertma@chromium.org> Commit-Queue: Luna Lu <loonybear@chromium.org> Cr-Commit-Position: refs/heads/master@{#606045} 07 November 2018, 15:20:45 UTC
9b9cf22 Žan Doberšek 07 November 2018, 14:09:12 UTC webkit: provide port name as run info (#13862) For the WebKit product, include the port name inside the run info, under the 'webkit_port' key. This will come in handy when disabling tests in metadata files for specific ports. 07 November 2018, 14:09:12 UTC
3b72925 jugglinmike 07 November 2018, 14:08:09 UTC [ci] Complete Docker image update (#13960) A recent patch updated the Docker image used by Taskcluster when building the project's `master` branch [1]. Update the corresponding configuration for tasks triggered by pull requests. This improves parity between the two processes, and because the new image is based on a more recent LTS release of Ubuntu, it reduces the likelihood of errors due to outdated system dependencies. [1] https://github.com/web-platform-tests/wpt/pull/13676 07 November 2018, 14:08:09 UTC
5cf3713 pyup.io bot 07 November 2018, 12:59:23 UTC Update pyflakes to 2.0.0 (#13925) 07 November 2018, 12:59:23 UTC
f30b2e0 Cameron McCormack 06 November 2018, 06:26:46 UTC Part 2: Serialize `background-size: auto auto` as "auto" With this change, all of Chrome, Edge, Firefox, and Safari serialize background-size by omitting the second "auto" if the value is "auto auto". Other keywords are still repeated. Depends on D10445 Differential Revision: https://phabricator.services.mozilla.com/D10446 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1501261 gecko-commit: e63ddbf2a29063f16922c6bd835fe716b8c9c10a gecko-integration-branch: autoland gecko-reviewers: firefox-style-system-reviewers, emilio 07 November 2018, 10:25:59 UTC
04eafef Cameron McCormack 06 November 2018, 06:26:45 UTC Part 1: Use Servo to serialize border-image-repeat With this change, all of Chrome, Edge, Firefox, and Safari serialize border-image-repeat by omitting a repeated keyword, so we update a WPT that was expecting duplicated keywords. Differential Revision: https://phabricator.services.mozilla.com/D10445 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1501261 gecko-commit: 4a37e18c3d3ca03ace2e543d843929db3aa3d267 gecko-integration-branch: autoland gecko-reviewers: firefox-style-system-reviewers, emilio 07 November 2018, 10:25:59 UTC
5f73e3a Geoff Brown 07 November 2018, 00:56:22 UTC Use mozdevice.launch_activity to start fennec/geckoview in web-platform tests bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1504931 gecko-commit: 4c0b9a5d991c1bdfe5f4a754cab6044b8b360a0e gecko-integration-branch: mozilla-inbound gecko-reviewers: kwierso 07 November 2018, 10:14:20 UTC
back to top