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

sort by:
Revision Author Date Message Commit Date
79001b1 Align resource timing buffer full processing to spec PR 168 (take 3) This change implements the processing model from PR 168[1], when it comes to setResourceTimingBufferSize(), clearResourceTimings() and the firing of the resourcetimingbufferfull event. This is a reland of [2] which is a reland of [3] (but with nicer tests). [1] https://github.com/w3c/resource-timing/pull/168 [2] https://chromium-review.googlesource.com/c/chromium/src/+/1350950 [3] https://chromium-review.googlesource.com/c/chromium/src/+/1345269 Bug: 908181, 908414 Change-Id: I3a6c6e9d6a9aa5b5f907d1e86bec701ff2fa022d Reviewed-on: https://chromium-review.googlesource.com/c/1373819 Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#615929} 17 December 2018, 12:01:57 UTC
6ac8aaf Update interfaces/webxr.idl (#14553) Source: https://github.com/tidoust/reffy-reports/blob/e64cb71/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/468885960 17 December 2018, 11:12:12 UTC
81f23a9 [css-text] Typo in Thai text Since we're testing dictionary based word-boundary detection, it seems quite important to avoid spelling mistakes. The Thai word “and” is spelled “และ” and not “แและ”. 17 December 2018, 08:35:02 UTC
0065f28 [css-text] Fix test It used an incorrect flag (ahem), and the description sentence was ambiguous. 17 December 2018, 08:19:06 UTC
75f5494 Delete tests that can never fail These tests claims to test overflow-wrap, but it never overflows, so the property never gets the chance to do anything. The description is also confusing, as it asks the reviewer to check things that cannot be seen visually: whether the black box is one or two rows cannot be seen, since they are contiguous. 17 December 2018, 06:34:46 UTC
a22f78b Remove incorrect tests Both these tests will render incorrectly if a specific font isn't available, and they don't install it themselves, making them misleading. Moreover, word-break-break-all-009's reference is just a copy of the test, and relies on automatic line breaking instead of manually inserted <br>s, so it will always pass. Finally, these tests could be fixed, but they are testing things that are already covered by other tests, so deleting them is appropriate. 17 December 2018, 04:43:24 UTC
7275e40 Verify TTFB in resource-timing.html WPT by measuring that the delay occurs between responseStart and responseEnd When simulating a delay after a statusline, measure that the delay is not included in the TTFB by measuring that it occurred between responseStart and responseEnd rather than requestStart and responseStart. This makes the tests less flaky when subject to shaky network and thread scheduling conditions, as might be present using Firefox's chaos mode. Bug: 568024 Change-Id: I0356f6256af6bc87fbb14860ed05472526c03e5d Reviewed-on: https://chromium-review.googlesource.com/c/1377725 Reviewed-by: Yoav Weiss <yoav@yoav.ws> Commit-Queue: Andrew Comminos <acomminos@fb.com> Cr-Commit-Position: refs/heads/master@{#617021} 17 December 2018, 04:29:13 UTC
6d3120b Add WPT to verify that 1XX responses are used to provide responseStart timing Verifies that the UA sets responseStart to the time that an initial 1XX response was received by returning {100, delay, 200} and testing that the delay is not included in responseStart. Bug: 568024 Change-Id: I7295e6478a95abe1b6154ddf1feab764f596a5ec Reviewed-on: https://chromium-review.googlesource.com/c/1372359 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#615853} 17 December 2018, 04:03:58 UTC
1a70ecd Remove unneeded tests These 4 tests are not technically wrong, but they are not automated, and they don't cover any aspect of the spec that isn't already covered by other tests. 17 December 2018, 04:02:53 UTC
11971ac Update <button type="menu"> test to reflect its removal <button type="menu"> got removed in https://github.com/whatwg/html/pull/2342 and this test was failing in all browsers. 16 December 2018, 14:14:12 UTC
4094d6a part 1: Include the 'unsafe' keyword in serializations of css-align properties. Previously we'd omit it since it was merely an explicit way of requesting the default behavior. But the spec has changed such that it's not necessarily equivalent to the default anymore: https://drafts.csswg.org/css-align/#overflow-values (Technically the behaviors are probably still equivalent in our implementation, pending bug 1451380, but we don't have to publicize that via our serialization.) Differential Revision: https://phabricator.services.mozilla.com/D14599 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1514309 gecko-commit: 4fe457a643097dd7f2b2245ed919a3106b532774 gecko-integration-branch: central gecko-reviewers: emilio 15 December 2018, 06:07:08 UTC
fcb8094 Fix gradient background sizing This is a hard-to-fix situation. We size generated background images according to the tile size, which is a snapped rectangle sized according to the destination values, in general. But then we compute a src rect for image drawing using the unsnapped values, because that is best for bitmap images where we want to pull out the most accurate src rect possible. However, that source rect ends up larger than the tile size due to rounding without the original offset in the layer (because now we are working in image space). The gradient painting code then sees that it has a src rect that is larger than the tile size and hence the gradient image size. The code thinks that we want to have some more pixels than the gradient provides, which is true in some cases, and scales things to get those extra pixels in the painted output. Hence empty pixels on the screen when we really want the gradient to be filling the dest rect. Changing the gradient painting code will break valid use cases. Changing the tile size breaks things in a different way and doesn't really fix the problem. So change the src rect computation to use snapped sizes for generated content in an attempt to get a src that matches the tile size. R=fmalita@chromium.org Bug: 898950 Change-Id: I100575ad4f4fa3004fbc232a72c90b0032ccef4e Reviewed-on: https://chromium-review.googlesource.com/c/1376814 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by: Florin Malita <fmalita@chromium.org> Cr-Commit-Position: refs/heads/master@{#616944} 15 December 2018, 04:22:09 UTC
a3efcf1 Update for RTCQuicStream.write() function. Combines functionality of finish() into write() by adding a new QuicStreamWriteParameters input parameter that includes a finish boolean. This is consistent with the latest spec draft and also adds symmetry between readInto() and write(). Bug: 874296 Change-Id: I0def0ca25587ebf00a4b179ce8e9e7a124c818f6 Reviewed-on: https://chromium-review.googlesource.com/c/1376720 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Steve Anton <steveanton@chromium.org> Commit-Queue: Seth Hampson <shampson@chromium.org> Cr-Commit-Position: refs/heads/master@{#616941} 15 December 2018, 04:07:11 UTC
ac42741 Ignore charset= in <meta content> if followed by unmatched quote. Differential Revision: https://phabricator.services.mozilla.com/D14410 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1469580 gecko-commit: d02d14a3dd6e172c4cc8efb5c749752d3893fc90 gecko-integration-branch: central gecko-reviewers: mrbkap 15 December 2018, 01:04:00 UTC
e183d86 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706 (#14530) 14 December 2018, 23:25:41 UTC
cf8b055 [CSS Transitions] Add test for reparenting As per https://github.com/w3c/csswg-drafts/issues/3309, any CSS Transition on a reparented element should be cancelled, as it leaves and then re-enters the Document. This already works on Chrome, Firefox, and Safari but fails on Edge. Bug: 902328 Change-Id: I097675a8146c8047417dd48193d0747216418cfb Reviewed-on: https://chromium-review.googlesource.com/c/1374742 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#616830} 14 December 2018, 21:39:41 UTC
ca3a8d6 Merge pull request #14511 from web-platform-tests/chromium-export-cl-1377129 [UserTiming] Fix mark-measure-return-null test 14 December 2018, 17:10:59 UTC
f6c4282 Ensure we call __wptrunner_process_next_event whenever we put a message on the queue 14 December 2018, 16:59:52 UTC
e4ba26c Make testharness tests run in a top-level browsing context Traditionally testharness tests ran in a auxillary browsing context opened using window.open and with access to the opener. This works well because the long-lived nature of the opener helps to avoid some of the race conditions that would otherwise occur. But it doesn't work *that* well; the recent refactor to stop continually focusing the opener broke tests that alter document.domain or otherwise prevent the opener being same-domain with the test window. And future platform features may cause the opener to be nulled out entirely so even a postMessage based fix wouldn't work. To solve all of this, this patch refactors things so that the initial window doesn't contain any logic at all and is just used to keep the browser alive between tests. Most of the logic moves to testharnessreport.js which is loaded once per test. In order to get the right timeout when timeout_multiplier is set this requires an addition to the product API in wptrunner to expose a function for getting the timeout multiplier. This allows us to get the timeout_multiplier for testharness tests upfront and avoids the need to change the content of testharnessreport when we start running testharness tests, or to restart the server for each test type. The main issue with the single-window implementation is that we need to start injecting script once the test page has loaded testharnessreport.js. For most browsers we are able to use pageLoadStrategy=eager to control this; in that case we can start running tests once DOMContentLoaded is reached. Chrome doesn't support this pageLoadStrategy, however, so we have to fake support with custom script. 14 December 2018, 16:59:52 UTC
3a8ff1c [LayoutTest] Split animations-parsing.html into two tests Currently it tests both style.animation and getComputedStyle.animation. This CL splits the test into two tests, one for style.animation, and the other one for getComputedStyle.animation such that each test is minimal. Bug: 772852 Change-Id: I3c3f43305497ffe9d91c4e3806efe2e65ff17806 Reviewed-on: https://chromium-review.googlesource.com/c/1378230 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#616677} 14 December 2018, 15:52:47 UTC
1dd43ed [UserTiming] Fix mark-measure-return-null test The test was incorrect per L2 spec: a void method 'returns' an undefined value, not a null object. This CL changes the test to show how to perform feature detection and compares L2 and L3 behavior. Bug: 914441 Change-Id: Id7173b2693d5bd42013dcdd25266d64fa8956e6a 14 December 2018, 15:51:03 UTC
4559dab Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html Attempt to stabilize in Gecko. Bug: 626744 Change-Id: Idfa06176948d1ffaf6ba8e65263bf5818ffd321b Reviewed-on: https://chromium-review.googlesource.com/c/1375875 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#616543} 14 December 2018, 15:42:53 UTC
ceebcb8 Regression test for crbug.com/626744 Bug: 626744 Change-Id: I4244c3f0316ceb55bc69655212f6677345b0a6cc Reviewed-on: https://chromium-review.googlesource.com/c/1374988 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#616311} 14 December 2018, 15:30:15 UTC
8a97b8a Use StyleColor for the stop-color property This changes the ComputedStyle storage for the stop-color property to be a StyleColor rather than a plain color. This fixes explicit inheritance for the property ('currentcolor' computes to itself). It also means we'll properly pick up changes to 'color'. Bug: 914728 Change-Id: I3c78a3615220b9149d1ea5102a6e5863526a6d51 Reviewed-on: https://chromium-review.googlesource.com/c/1377437 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#616660} 14 December 2018, 14:39:38 UTC
6c14d36 [wptrunner] Correct support for eager page loading Many reftests schedule behavior to occur when the document reaches the "complete" readyState by setting the `onload` property of the document element. Previously, the automation scripts were written to conditionally defer execution for that event by setting the `onload` property of the global object. The two strategies are mutually exclusive. The sequence of script execution is not controlled, so either consumer of the "load" event could be blocked by the other. Update the automation scripts to register for the event using `addEventListener` in order to avoid unintended interaction with test code. 14 December 2018, 14:26:09 UTC
506442f Update requests from 2.20.1 to 2.21.0 14 December 2018, 14:25:17 UTC
f378387 Serialize animation in the right order Per spec: https://drafts.csswg.org/css-animations/#animation The name of the animation should be the end of the value list, to avoid ambiguity when serializing/deserializing the animation. This CL fixes the problem for both element.style and the window.getComputedStyle. A wpt test is added. Since this CL changes the output of an existing web API, an Intent to Ship has been sent to blink-dev and 3 LGTMs has been granted. https://groups.google.com/a/chromium.org/forum/?utm_medium=email&utm_source=footer#!msg/blink-dev/KUelGRZP73Y/F4YxTGBOBwAJ Bug: 772852 Change-Id: I88b06b57c68013d99c8c4fd4bd39bdfcf9b807fc Reviewed-on: https://chromium-review.googlesource.com/c/1367935 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#616639} 14 December 2018, 12:07:35 UTC
ed62f0a Fix serialization of explicitly case-sensitive attr selectors with a namespace. Differential Revision: https://phabricator.services.mozilla.com/D14493 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1514029 gecko-commit: a704ad19e3ad3ce99f3aa5addfc57c144e54c4fd gecko-integration-branch: central gecko-reviewers: emilio 14 December 2018, 11:04:39 UTC
68a96eb Fix <table> having "column-span:all" style. The main style of <table> is set on the inner TableFrame, not the outer TableWrapperFrame. Thus, we fail to spot the table as a column-span kid in nsCSSFrameConstructor::ConstructionBlock(). Differential Revision: https://phabricator.services.mozilla.com/D13957 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1506306 gecko-commit: 5b7718956a45cb09019e4bd8aabd23bee6e3d0f0 gecko-integration-branch: autoland gecko-reviewers: bzbarsky 14 December 2018, 10:37:21 UTC
15886f0 Ignore adopted stylesheets from different document tree If we adopt a subtree containing a shadowRoot that has adoptedStyleSheets from one document to a different document, the adoptedStyleSheets will be moved along with it. We want to ignore the stylesheets that are constructed in a different document tree when we're doing style calculation. Draft spec: https://wicg.github.io/construct-stylesheets/ Bug: 807560 Change-Id: If36676e642b5d1b5c1c403c14cc24be8e670f153 Reviewed-on: https://chromium-review.googlesource.com/c/1377486 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#616621} 14 December 2018, 09:52:06 UTC
1a74566 Change wpt crash handling API to be a single method Because mozcrash is stateful we can't check for crashes and then later log them; we need to do everything in one shot. Therefore remove the check_for_crashes call, rename log_crash to check_crash and make it return a boolean indicating whether any crashes occured, as well as handling the logging. Differential Revision: https://phabricator.services.mozilla.com/D14437 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1513927 gecko-commit: 517fdabf94bdc2eaceb697e6098d14ce649ba93c gecko-integration-branch: autoland gecko-reviewers: ted 14 December 2018, 07:32:30 UTC
e1d7b9d Handle nested slots correctly in slotted matching and invalidation. The patch and test should be pretty much self-descriptive. Differential Revision: https://phabricator.services.mozilla.com/D14063 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1512026 gecko-commit: 7b04cdcfdcf4f7e071df42fd19d29c79f1786db5 gecko-integration-branch: autoland gecko-reviewers: heycam 14 December 2018, 04:56:35 UTC
443fc38 Ensure we only load the wpt test types we requested Differential Revision: https://phabricator.services.mozilla.com/D14438 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1513580 gecko-commit: bfca182e8a80c68fc78b3dde6626fa53fec50cc9 gecko-integration-branch: autoland gecko-reviewers: Ms2ger 14 December 2018, 03:47:36 UTC
1db8f79 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192685 (#14516) 14 December 2018, 03:21:45 UTC
c85f06e clear.py relies on old Gecko's <button> hit testing bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1498383 gecko-commit: 7029e8b4d7d01b8c62cc366c215a2f187dc03782 gecko-integration-branch: mozilla-inbound gecko-reviewers: ato 14 December 2018, 01:34:28 UTC
e75e7b6 Return used width/height for SVG <image>, <rect> and <foreignObject> Per https://drafts.csswg.org/cssom/#resolved-values we should return the "used value" for 'width' and 'height' on these elements [1]. This behavior was clarified in SVGWG GitHub issue #349 [2]. [1] And also on <svg>, but we don't support those properties there yet. Tests added for that case too though. [2] https://github.com/w3c/svgwg/issues/349 Bug: 772707 Change-Id: Ic7b6b148883d4380daadb41b62bddd02da55e1af Reviewed-on: https://chromium-review.googlesource.com/c/1374291 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#616343} 13 December 2018, 17:39:51 UTC
04c862e Update interfaces/webrtc-stats.idl (#14490) Source: https://github.com/tidoust/reffy-reports/blob/1d1a9ed/whatwg/idl/webrtc-stats.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/467371826 13 December 2018, 13:56:14 UTC
9377b49 Revert "Make testharness tests run in a top-level browsing context" (#14496) This reverts commit 74522a275bea481821e789145578e9e16fd27be3. Fixes https://github.com/web-platform-tests/wpt/issues/14495. Reopens https://github.com/web-platform-tests/wpt/issues/13418. 13 December 2018, 09:46:54 UTC
bc5122d service worker: XSLT: Use response URL for the base URL. This aligns with the standard. See https://github.com/whatwg/fetch/pull/146 Chrome Status: https://www.chromestatus.com/feature/4857368017895424 No intent to ship because it's a trivial change. Bug: 914135 Change-Id: I229aec6f8473bb6b7cdc88429afa830bc6eb80ed Reviewed-on: https://chromium-review.googlesource.com/c/1372109 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#616248} 13 December 2018, 08:53:47 UTC
483983d [resource-timing] Avoid race condition Depending on the scheduling of resource retrieval, performance entries for the test harness files may be observable by this test. That behavior is beyond the focus of this test, so such entries should be ignored if present. 13 December 2018, 08:07:49 UTC
16b2635 Fix Headers mutation with "request-no-cors" guard https://github.com/whatwg/fetch/pull/833 Bug: 905677 Change-Id: Ie4141c2b900931ef88e7734cb152b6d28955999f Reviewed-on: https://chromium-review.googlesource.com/c/1352075 Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#616230} 13 December 2018, 06:52:46 UTC
f0e18fa Move constructable stylesheets layout test to WPT We're shipping constructable stylesheets soon, so moving the layout test to WPT now. Draft spec: https://wicg.github.io/construct-stylesheets/index.html Bug: 807560 Change-Id: I37b45b6bbb1b17da51fbc41fbac5f11caabc5070 Reviewed-on: https://chromium-review.googlesource.com/c/1375296 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#616226} 13 December 2018, 06:15:24 UTC
e90dc47 Reland "Fix SVG-As-Background sizing" This is a reland of aed99d7e12bd036ab3ebb4fe522ce8faf347a32f It was reverted in https://chromium-review.googlesource.com/c/chromium/src/+/1373285 But the real culprit is a recipe change which is being reverted in https://chromium-review.googlesource.com/c/chromium/tools/build/+/1373509 Original change's description: > Fix SVG-As-Background sizing > > Addresses a TODO where we were snapping the intrinsic size of an SVG image, > even when that is no longer useful. This was posing issues with operations > using aspect ratio, because the computed aspect ratio on the snapped value > was wrong when then used on un-snapped values. > > R=fs@opera.com > BUG=855882 > > Change-Id: I0c14c0109da4c5ca5e52aebf408e9b702eda799c > Reviewed-on: https://chromium-review.googlesource.com/c/1370486 > Commit-Queue: Stephen Chenney <schenney@chromium.org> > Reviewed-by: Fredrik Söderquist <fs@opera.com> > Cr-Commit-Position: refs/heads/master@{#615798} Bug: 855882 Change-Id: Icdd1ad0af2aaae6f633b8940522115e9742d1d7f Reviewed-on: https://chromium-review.googlesource.com/c/1373286 Reviewed-by: Shuotao Gao <stgao@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#615840} 13 December 2018, 04:44:28 UTC
beeeae3 [LayoutNG] Exclude trailing preserved spaces when avoiding floats This patch fixes an interoperability issue where trailing preserved spaces should be excluded when avoiding floats. All 4 implementations are interoperable on this regard. This patch adds NGLineInfo::HasOverflow(), because knowing whether the line has overflow or not is easy and fast, while knowing the exact inline size excluding trailing preserved spaces may involve reshaping. Other cases also have interoperability problems, such as `text-align` or `min-content`. I'll investigate them in following patches. Bug: 913995 Change-Id: Ibf13f1fcc28bbd99d44b56611141efa49d6d1c89 Reviewed-on: https://chromium-review.googlesource.com/c/1374329 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#616155} 13 December 2018, 02:08:33 UTC
4052654 [EventTiming] Report events without event handlers This CL allows reporting events without event handlers. In particular, this implies that slow clicks cause slow mousedown events, so the tests are modified accordingly. Bug: 823744 Change-Id: I9578519ae538496404bb220001d3ca97565b7bd7 Reviewed-on: https://chromium-review.googlesource.com/c/1368458 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#616026} 12 December 2018, 21:40:13 UTC
05ccfd8 Revert "Fix SVG-As-Background sizing" This reverts commit aed99d7e12bd036ab3ebb4fe522ce8faf347a32f. Reason for revert: Speculative revert for the compile failure on Android and ChromeOS, because this CL is the single CL that shows up in the blamelist of both failed builds. https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/android-rel/5507 https://ci.chromium.org/buildbot/chromium.chrome/Google%20Chrome%20ChromeOS/59554 Original change's description: > Fix SVG-As-Background sizing > > Addresses a TODO where we were snapping the intrinsic size of an SVG image, > even when that is no longer useful. This was posing issues with operations > using aspect ratio, because the computed aspect ratio on the snapped value > was wrong when then used on un-snapped values. > > R=​fs@opera.com > BUG=855882 > > Change-Id: I0c14c0109da4c5ca5e52aebf408e9b702eda799c > Reviewed-on: https://chromium-review.googlesource.com/c/1370486 > Commit-Queue: Stephen Chenney <schenney@chromium.org> > Reviewed-by: Fredrik Söderquist <fs@opera.com> > Cr-Commit-Position: refs/heads/master@{#615798} TBR=fs@opera.com,schenney@chromium.org Change-Id: I6bd43ac3ad23393be353249657566e9080cd69c0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 855882 Reviewed-on: https://chromium-review.googlesource.com/c/1373285 Reviewed-by: Shuotao Gao <stgao@chromium.org> Commit-Queue: Shuotao Gao <stgao@chromium.org> Cr-Commit-Position: refs/heads/master@{#615831} 12 December 2018, 21:21:46 UTC
c3f2a6c Merge pull request #14435 from web-platform-tests/beaufortfrancois-patch-1 Fix timeout issue by calling play() 12 December 2018, 19:40:40 UTC
d3ad404 Wake Lock API: Add checks for feature policy. Added checks for feature policy attribute. This fixes all feature policy related tests. BUG=862460,257511 Change-Id: I6258c41dcca164f7c6584ba4a387860237ca3ba3 Reviewed-on: https://chromium-review.googlesource.com/c/1343193 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Mrunal Kapade <mrunal.kapade@intel.com> Cr-Commit-Position: refs/heads/master@{#615985} 12 December 2018, 19:35:32 UTC
ab0f311 make <button> hit testing similar to other elements which may have some content, and for click target find the common (interactive) ancestor bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1089326 gecko-commit: 36b949bef79831ec07807ffa4aead2e60f5f7409 gecko-integration-branch: mozilla-inbound gecko-reviewers: masayuki 12 December 2018, 18:50:45 UTC
0a1f5ea Add PerformanceObserver.supportedEntryTypes Blink intent: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/XZU_DhQ9ZGs Bug: 911314 Change-Id: I4a79d6d3a81ec260c7db5c2bea7b2d533a1285b2 Reviewed-on: https://chromium-review.googlesource.com/c/1359480 Reviewed-by: Yoav Weiss <yoav@yoav.ws> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#615924} 12 December 2018, 17:06:41 UTC
becea77 Reland "Create RTCDtlsTransport objects in the blink layer" This reverts commit 68c1d92a3636682a92cd7db078898fcdb4e2a191. Reason for revert: Fixed an issue that fits the symptoms Original change's description: > Revert "Create RTCDtlsTransport objects in the blink layer" > > This reverts commit d7d59c5b7e4110ba0a7c1752387fb1b5ea0282cb. > > Reason for revert: virtual/webrtc-wpt-unified-plan/external/wpt/webrtc/RTCRtpSender-transport.https.html fails in "WebKit Linux Trusty MSAN". > > Original change's description: > > Create RTCDtlsTransport objects in the blink layer > > > > This CL does on-demand creation of blink-layer transport > > objects. It also introduces a way to get at the webrtc::PeerConnection > > object from the WebPeerConnectionHandler API. > > > > Bug: chromium:907849 > > Change-Id: Ic86a5a66289c31d1f939a47d58bc194c32471cbd > > Reviewed-on: https://chromium-review.googlesource.com/c/1358060 > > Commit-Queue: Harald Alvestrand <hta@chromium.org> > > Reviewed-by: Guido Urdaneta <guidou@chromium.org> > > Reviewed-by: Henrik Boström <hbos@chromium.org> > > Reviewed-by: Kentaro Hara <haraken@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#615072} > > TBR=hta@chromium.org,haraken@chromium.org,hbos@chromium.org,guidou@chromium.org > > Change-Id: Ie9c8d2e3dc5f97fc94ca5bf43cc30a9407d9fa4c > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: chromium:907849 > Reviewed-on: https://chromium-review.googlesource.com/c/1369719 > Reviewed-by: Samuel Huang <huangs@chromium.org> > Commit-Queue: Samuel Huang <huangs@chromium.org> > Cr-Commit-Position: refs/heads/master@{#615115} Change-Id: Ic0dcb6851d725eec31fb4203770cd21b88ce3e88 Bug: chromium:907849 Reviewed-on: https://chromium-review.googlesource.com/c/1371890 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Florent Castelli <orphis@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#615915} 12 December 2018, 16:41:40 UTC
305ff11 Encoding: make it clear sniffing for UTF-8 is not acceptable See https://github.com/whatwg/encoding/issues/68 for background. 12 December 2018, 06:10:46 UTC
bdd6d95 Make <input type=range> min-content size the same as its max-content size (not zero). bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1512066 gecko-commit: b64bce5682de55adc29682f6077b75d61cc9d849 gecko-integration-branch: mozilla-inbound gecko-reviewers: jwatt 12 December 2018, 05:59:54 UTC
39f6169 Fix SVG-As-Background sizing Addresses a TODO where we were snapping the intrinsic size of an SVG image, even when that is no longer useful. This was posing issues with operations using aspect ratio, because the computed aspect ratio on the snapped value was wrong when then used on un-snapped values. R=fs@opera.com BUG=855882 Change-Id: I0c14c0109da4c5ca5e52aebf408e9b702eda799c Reviewed-on: https://chromium-review.googlesource.com/c/1370486 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#615798} 12 December 2018, 03:05:29 UTC
9bf305b SVG: percentages reference viewport dimensions (#14447) WPT for https://github.com/w3c/svgwg/pull/615 % cx,rx,x,width reference viewport width % cy,ry,y,height reference viewport height % r,stroke-width,stroke-dasharray,stroke-dashoffset reference normalized viewport diagonal, i.e. diagonal/sqrt(2). 12 December 2018, 00:21:25 UTC
48d5d50 MSE: Update one of the wpt mediasource-errors sub-tests Updates one of the subtests to be less tightly bound to one implementation's scheduling of append error algorithm versus readyState transitions to HAVE_METADATA when one appendBuffer could potentially cause both. Change-Id: I50f98c2815014aacd67cb27bfc3d71ba50a16ab4 Reviewed-on: https://chromium-review.googlesource.com/c/1371166 Reviewed-by: Dan Sanders <sandersd@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#615709} 11 December 2018, 23:09:32 UTC
e265806 Async Clipboard: Update tests to use async/await syntax Bug: 896479 Change-Id: I95b4c57b2643883f2ea7f0ebbea4f50d7bc7111a Reviewed-on: https://chromium-review.googlesource.com/c/1371016 Reviewed-by: Gary Kacmarcik <garykac@chromium.org> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#615686} 11 December 2018, 22:33:00 UTC
ead04bd [Gecko Bug 1512264] webdriver: reuse http connection in test client (#14439) * webdriver: reuse http connection in test client Whilst we do set the Keep-Alive HTTP header to request the HTTPD to use a persistent connection, we throw away the httplib.HTTPConnection object after each request. This will causes the HTTPD to serve us a persistent connection, only to throw it away after the first request. When the connection timeout is reached, httplib closes the connection for us. Unfortunately httplib does not reconnect for the next request, so we need to manually check if the underlying socket connection to the server is alive. We check whether the connection has dropped or if it has unread, buffered data using select() as a poller. We could use poll() here on available systems, which might give a theoretical performance improvement since it gives O(number of file descriptors), but since we only deal with one connection select() will probably be good enough. Differential Revision: https://phabricator.services.mozilla.com/D13845 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1512264 gecko-commit: ac21c2e0b04095d582411393f0f06318c67d407b gecko-integration-branch: autoland gecko-reviewers: jgraham * Update transport.py * Update tools/webdriver/webdriver/transport.py Co-Authored-By: jgraham <james@hoppipolla.co.uk> 11 December 2018, 21:45:12 UTC
7750d16 [Azure Pipelines] Enable TBPL logging for infrastructure/ tests (#14454) Chrome Dev failed in https://dev.azure.com/web-platform-tests/wpt/_build/results?buildId=1865 for unknown reasons, so enable TBPL logging to make it possible to get the logs and use reftest analyzer. 11 December 2018, 21:18:23 UTC
bbdfa0a Make SSL tests work in servodriver. 11 December 2018, 19:30:05 UTC
60ba182 Add headless support to servodriver harness. 11 December 2018, 19:30:05 UTC
c522b88 Remove reference to missing run() function in CSS tests 11 December 2018, 17:16:03 UTC
ecf5c9a Fix document.write tests to not assume globals exist after document.open 11 December 2018, 17:16:03 UTC
74522a2 Make testharness tests run in a top-level browsing context Traditionally testharness tests ran in a auxillary browsing context opened using window.open and with access to the opener. This works well because the long-lived nature of the opener helps to avoid some of the race conditions that would otherwise occur. But it doesn't work *that* well; the recent refactor to stop continually focusing the opener broke tests that alter document.domain or otherwise prevent the opener being same-domain with the test window. And future platform features may cause the opener to be nulled out entirely so even a postMessage based fix wouldn't work. To solve all of this, this patch refactors things so that the initial window doesn't contain any logic at all and is just used to keep the browser alive between tests. Most of the logic moves to testharnessreport.js which is loaded once per test. In order to get the right timeout when timeout_multiplier is set this requires an addition to the product API in wptrunner to expose a function for getting the timeout multiplier. This allows us to get the timeout_multiplier for testharness tests upfront and avoids the need to change the content of testharnessreport when we start running testharness tests, or to restart the server for each test type. The main issue with the single-window implementation is that we need to start injecting script once the test page has loaded testharnessreport.js. For most browsers we are able to use pageLoadStrategy=eager to control this; in that case we can start running tests once DOMContentLoaded is reached. Chrome doesn't support this pageLoadStrategy, however, so we have to fake support with custom script. 11 December 2018, 17:16:03 UTC
5dd605c Implement RTCRtpReceiver.getParameters() Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/LXJUzctTVfM/p4J-WrzbBgAJ Bug: 908911 Change-Id: I8e82cc588fb991458e2372fe1dcb9db459cd36b5 Reviewed-on: https://chromium-review.googlesource.com/c/1363276 Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/master@{#615518} 11 December 2018, 14:49:15 UTC
93ee6d0 HTML: also test syntax errors 11 December 2018, 14:22:55 UTC
0d4b277 Wait for wpt tests to finish across reloads When wpt is used by developers they often want to reload a test that's running to allow iterative development (or running under devtools, etc.). The recent switch to target marionette commands at the test window rather than the opener window broke this as waiting is implemented as an async script that never returns (i.e. a promise that never resolves) and when this is in the test window navigating that window causes the script to return. A simple, but not particuarly elegant, solution here is to simply rerun the script in the new window. Differential Revision: https://phabricator.services.mozilla.com/D14087 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1513023 gecko-commit: 0a36f92c457acb05b5f9ee147c3ae42a8a6d9de3 gecko-integration-branch: autoland gecko-reviewers: ato 11 December 2018, 14:08:38 UTC
e3de058 Fix import from serve.serve for local fennec wpt runs Differential Revision: https://phabricator.services.mozilla.com/D13884 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1512320 gecko-commit: b58ea9ea4468244fdad1b7f5cb1626e9f0ad01e3 gecko-integration-branch: autoland gecko-reviewers: jgraham 11 December 2018, 13:57:25 UTC
69d00d5 HTML: test that non-synthetic errors get muted too 11 December 2018, 12:44:34 UTC
22de4b6 Add tests for event handler when body is a frameset (#12664) Combine and optimize the code with existing tests. 11 December 2018, 12:37:26 UTC
37cd0d6 [Azure Pipelines] Clarify the job dependencies by reordering/renaming (#14459) With the affected test jobs, the root job is no longer *the* root. Use "decision" following the terminology of Taskcluster: https://docs.taskcluster.net/docs/tutorial/gecko-decision-task 11 December 2018, 11:03:45 UTC
b3a21df Update expectations for infrastructure/ (#14457) Related: https://github.com/web-platform-tests/wpt/issues/14456 11 December 2018, 11:00:56 UTC
19d3a23 WPT: CSS: Add same-origin tests for loading error stylesheets. This adds a test that a stylesheet that failed to load is considered cross-origin. That is, accessing |styleSheet.rules| throws a SecurityError. This aligns with the specifications: - cssRules checks the `origin-clean` flag: https://drafts.csswg.org/cssom/#dom-cssstylesheet-cssrules - This is set to true iff CORS-same-origin: https://html.spec.whatwg.org/multipage/links.html#link-type-stylesheet - CORS-same-origin is false for "error" responses: https://html.spec.whatwg.org/multipage/urls-and-fetching.html#cors-same-origin Bug: 911974 Change-Id: I558e6d3dfa564b15284c393ffc35b80f54a9bc4e Reviewed-on: https://chromium-review.googlesource.com/c/1371307 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#615479} 11 December 2018, 10:47:58 UTC
600dd6c WPT: CSS: Add cross-origin redirect tests. This adds tests that stylesheets that result from requests that were redirected cross-origin are considered cross-origin. Note that A->B->A redirects, which redirect from cross-origin to same-origin, are considered cross-origin. See https://github.com/whatwg/fetch/issues/737 and https://github.com/whatwg/fetch/pull/834. In Blink, we have redirect tests at http/tests/security/cannot-read-cssrules-redirect.html. This WPT addition will supersede that test, but I won't yet remove it since it asserts the opposite for the A->B->A case. I can remove the test when Blink changes to pass this WPT test. Bug: 911974 Change-Id: Ie015c0390829299de7c29cff6685ddfcd774c66f Reviewed-on: https://chromium-review.googlesource.com/c/1370162 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#615475} 11 December 2018, 10:28:36 UTC
5b1a757 Add support for 's' flag on attribute selectors. We could keep using ParsedCaseSensitivity::CaseSensitive as a temporary stand-in for "case-sensitive or maybe not depending on what HTML says" until we check the attribute list, but it seems better to make that explicit. Differential Revision: https://phabricator.services.mozilla.com/D14093 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1512386 gecko-commit: bfd73976f27e1dc2b64f0203f9460f726e3ebedd gecko-integration-branch: autoland gecko-reviewers: emilio 11 December 2018, 10:05:17 UTC
5e118a9 [Azure Pipelines] Run affected tests on Safari Technology Preview (#14156) 11 December 2018, 09:53:24 UTC
9f42aa0 Suppress flake8 error about bare except. (#14450) 11 December 2018, 09:40:25 UTC
1a75f34 HTML: add more protocol handlers tests - Imported and merged protocol handler tests from chromium(https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/blink/web_tests/http/tests/navigatorcontentutils) - Fixed bug that it should throw SecurityError with invalid schemes - Did some code optimization 11 December 2018, 08:59:33 UTC
703b3a7 Fix generate-test-certs.sh script Openssl does not take --subj parameter, but -subj. Bug: 803774 Change-Id: Ie5e1da18941468fc66ea567134a49178b4260aba Reviewed-on: https://chromium-review.googlesource.com/c/1370177 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Rob Buis <rbuis@igalia.com> Cr-Commit-Position: refs/heads/master@{#615459} 11 December 2018, 08:09:19 UTC
e35021b [CSS] Fix test for css invalidation so that it fails without ::part. The test was testing that the element ended up green (starting red) however, if the browser has no support at all for ::part then the element actually starts green and stays green. Bug: 805271 Change-Id: Ida40c7963aa3a00c3d197b1309ddaea49e4f3b92 Reviewed-on: https://chromium-review.googlesource.com/c/1369500 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#615435} 11 December 2018, 05:52:01 UTC
912d508 Add a test for dealing with multiple image loading tasks when the list of available images is usable. 11 December 2018, 01:57:16 UTC
e4a221e [ScrollTimeline] Upstream root scroller currentTime test to WPT This CL upstreams the root scroller currentTime test to WPT. The quirks mode test is left in fast/animation/scroll-animations as it is just a crash test for running in quirks mode, which is Chrome-specific and not upstreamable. There are no behavioral changes. Bug: 911254 Change-Id: Ia8270f11ede8746cbdecf7ba57aeca60eee6fb78 Reviewed-on: https://chromium-review.googlesource.com/c/1366367 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#615225} 10 December 2018, 20:36:13 UTC
8eab58f [WebCryptoAPI] Remove race condition (#14291) * [WebCryptoAPI] Remove race condition Configure testharness.js to wait until the global `done` function is invoked before reporting results. This ensures that all asynchronously-declared tests are defined and subsequently executed regardless of variations in timing. * fixup! [WebCryptoAPI] Remove race condition 10 December 2018, 18:31:21 UTC
ee999c2 Add WPT tests for correct parsing of msid Bug: None Change-Id: Ib12aa3660a1b1d2c350d7fd81aaff810b3d979cc Reviewed-on: https://chromium-review.googlesource.com/c/1365443 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#615145} 10 December 2018, 16:47:56 UTC
e177591 [ScrollTimeline] Upstream NaN currentTime tests to WPT This CL upstreams the NaN related currentTime tests to WPT. There are no behavioral changes. Bug: 911254 Change-Id: Ide27accae72cc55654890754ac404c7827889d09 Reviewed-on: https://chromium-review.googlesource.com/c/1366264 Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#615137} 10 December 2018, 16:43:37 UTC
9ed4d9b [ChromeDriver] Make some mouse web platform tests work on wpt serve (#14304) I have changed ExecutePerformActions function in window_commands.cc to execute the actions input sent from Webdriver and convert an element in origin into coordinates. Bug: chromedriver:1897 Change-Id: I407dbad5e001f15ddd4edfd709f5460384e95530 Reviewed-on: https://chromium-review.googlesource.com/c/1356123 Reviewed-by: John Chen <johnchen@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#614838} 10 December 2018, 16:22:42 UTC
26390b3 [ScrollTimeline] Upstream writing-mode currentTime tests to WPT This CL upstreams the writing-mode related currentTime tests to WPT. There are a few mostly non-behavioral changes to the tests in this CL: * Some comments were edited for clarity. * For tests with more than one assert_equals(), descriptions were added to the asserts. This is to help locate failing assert_equal lines, as jsharness does not print out the line number of a failure. * In a few places we had more than one assert_equals for the same scenario (e.g. multiple cases where scroll was after the startScrollOffset point). These have been deduplicated. Bug: 911254 Change-Id: I5e814acea281e2587164de634da9a5415b53de2c Reviewed-on: https://chromium-review.googlesource.com/c/1366263 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#615126} 10 December 2018, 15:56:39 UTC
8832bcc Revert "Create RTCDtlsTransport objects in the blink layer" This reverts commit d7d59c5b7e4110ba0a7c1752387fb1b5ea0282cb. Reason for revert: virtual/webrtc-wpt-unified-plan/external/wpt/webrtc/RTCRtpSender-transport.https.html fails in "WebKit Linux Trusty MSAN". Original change's description: > Create RTCDtlsTransport objects in the blink layer > > This CL does on-demand creation of blink-layer transport > objects. It also introduces a way to get at the webrtc::PeerConnection > object from the WebPeerConnectionHandler API. > > Bug: chromium:907849 > Change-Id: Ic86a5a66289c31d1f939a47d58bc194c32471cbd > Reviewed-on: https://chromium-review.googlesource.com/c/1358060 > Commit-Queue: Harald Alvestrand <hta@chromium.org> > Reviewed-by: Guido Urdaneta <guidou@chromium.org> > Reviewed-by: Henrik Boström <hbos@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Cr-Commit-Position: refs/heads/master@{#615072} TBR=hta@chromium.org,haraken@chromium.org,hbos@chromium.org,guidou@chromium.org Change-Id: Ie9c8d2e3dc5f97fc94ca5bf43cc30a9407d9fa4c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:907849 Reviewed-on: https://chromium-review.googlesource.com/c/1369719 Reviewed-by: Samuel Huang <huangs@chromium.org> Commit-Queue: Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#615115} 10 December 2018, 15:20:38 UTC
eedce7c rel=noopener implicit for target=_blank in anchor and area elements when no rel attribute is set - WPT bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503681 gecko-commit: 45e6f25036c57ad42140e749bb2927e5365d038c gecko-integration-branch: mozilla-inbound gecko-reviewers: annevk 10 December 2018, 14:10:48 UTC
94ac45d Reland "Find manifest for download by tags instead of commits" Reverted in https://github.com/web-platform-tests/wpt/pull/14208 as possible cause of https://github.com/web-platform-tests/wpt/issues/14207. This reverts commit 5438f72ea0bc2abb3754b2b906a34d497bd8457c. 10 December 2018, 13:56:29 UTC
18bb80e Add muted error tests for redirected scripts Helps with https://github.com/whatwg/fetch/issues/737. 10 December 2018, 13:24:44 UTC
b9825de Treat more "no-cors" image loads as cross-origin In particular when it's redirected from same-origin to cross-origin to same-origin. Or cross-origin to same-origin. (Relative to the document responsible for the fetch.) 10 December 2018, 13:23:37 UTC
97a0309 Don't estimate the top of bottom-aligned OOFs as bottom. (This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/1355920 with proper rebaselining) We'll incorrectly think that we get fragmented in that case, which will lead to incorrect height, which will lead to incorrect top offset, which will lead to incorrect fragmentation. This has probably been the cause for a flaky web test, that behaved even worse in LayoutNG, because in NG we force legacy layout as soon as fragmentation is involved (so when entering printing, we typically need to rebuild the entire layout object tree, with no former height to base the bottom estimate on (which is what saved us when NG is disabled - ehm, at least most of the time)). TBR=atotic@chromium.org,eae@chromium.org Bug: 910300 Change-Id: I00bce89900c50d6db9b39a4b72dbd6ab653184a7 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1365436 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#615089} 10 December 2018, 11:51:18 UTC
503a714 Use wpt run --affected on Taskcluster 10 December 2018, 10:13:21 UTC
837e5b7 Implement --affected as a flag of `wpt run` This is squashed and pulled from #14156 , with the unrelated changes removed (namely the Safari setup in .azure-pipelines.yml), and some review comments addressed. 10 December 2018, 10:13:21 UTC
902b4ca Fix timeout issue by calling play() 10 December 2018, 10:12:29 UTC
acc3783 Create RTCDtlsTransport objects in the blink layer This CL does on-demand creation of blink-layer transport objects. It also introduces a way to get at the webrtc::PeerConnection object from the WebPeerConnectionHandler API. Bug: chromium:907849 Change-Id: Ic86a5a66289c31d1f939a47d58bc194c32471cbd Reviewed-on: https://chromium-review.googlesource.com/c/1358060 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#615072} 10 December 2018, 10:12:06 UTC
a4bbfb3 Make sure that Actions.perform is always passed a list (#14345) 10 December 2018, 10:10:17 UTC
a00b58d Updated hyper so that it uses the third_party/h2 instead of its own version of h2 10 December 2018, 10:02:54 UTC
9f2b713 Remove test-level assert property from tests (#14409) Test-level asserts is the only remaining use of is for test-level assert metadata. Remove all the assert property from tests and mark them as test comments if possible. For `help` and `author`, moving the information to the top of the test files. Fixes #14394. 10 December 2018, 09:53:50 UTC
back to top