5b63b180963c7d79887342f0a7342868088cd542: Bug 1497198 [wpt PR 13421] - Use conditionals to avoid running no-op jobs on Travis, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:54 +0000 - rev 441044
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497198 [wpt PR 13421] - Use conditionals to avoid running no-op jobs on Travis, a=testonly Automatic update from web-platform-testsUse conditionals to avoid running no-op jobs on Travis See documentation: https://docs.travis-ci.com/user/conditional-builds-stages-jobs/ https://docs.travis-ci.com/user/conditions-v1 -- wpt-commits: 058b8824487518df2dece6a95ec5e4d71d4b9ad1 wpt-pr: 13421
a88e4b2e5274eae2857c8e5c0e518f44c836d544: Bug 1497125 [wpt PR 13414] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 08 Oct 2018 21:14:25 +0000 - rev 441043
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497125 [wpt PR 13414] - Update wpt metadata, a=testonly wpt-pr: 13414 wpt-type: metadata
e9ac63863da9a9b1fa0d3988da3e5b1efb77675d: Bug 1497125 [wpt PR 13414] - Make :host account for its own pseudo-class specificity., a=testonly
Rune Lillesveen <futhark@chromium.org> - Thu, 11 Oct 2018 09:31:49 +0000 - rev 441042
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497125 [wpt PR 13414] - Make :host account for its own pseudo-class specificity., a=testonly Automatic update from web-platform-testsMake :host account for its own pseudo-class specificity. Otherwise `:host div` is equally specific to `div`, which seems undesirable and doesn't match any spec. This is only done for Shadow DOM v1 since there are backward compat issues with Polymer and WebUI. Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/gYrR2nR6quI Bug: 857415 Change-Id: Ieaaf9b835ae7136806ced8f6e72fb30f9adf02af Reviewed-on: https://chromium-review.googlesource.com/c/1250963 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Emilio Cobos Álvarez <emilio@chromium.org> Cr-Commit-Position: refs/heads/master@{#597549} -- wpt-commits: 5810d070c87063deb718734562e8e2340efacdf1 wpt-pr: 13414
4d86700418d293e5e4deacf559b76b6cac6ad046: Bug 1497185 [wpt PR 13420] - Remove tools/wptserve/.travis.yml, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:47 +0000 - rev 441041
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497185 [wpt PR 13420] - Remove tools/wptserve/.travis.yml, a=testonly Automatic update from web-platform-testsRemove tools/wptserve/.travis.yml It's no longer used after wptserve was merged into this repo. -- wpt-commits: ddf2b44f5e112c535247a38cb0b058bc48b8e20a wpt-pr: 13420
5fcb3470239e64906db361514e5a956cd638a227: Bug 1497163 [wpt PR 13388] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 08 Oct 2018 21:10:54 +0000 - rev 441040
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497163 [wpt PR 13388] - Update wpt metadata, a=testonly wpt-pr: 13388 wpt-type: metadata
c1b374a8deaf00ab2c25e5af0dd6e10338f5c75c: Bug 1497163 [wpt PR 13388] - [LayoutNG] Correct LayoutText::LinesBoundingBox() for vertical-rl., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 11 Oct 2018 09:31:43 +0000 - rev 441039
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497163 [wpt PR 13388] - [LayoutNG] Correct LayoutText::LinesBoundingBox() for vertical-rl., a=testonly Automatic update from web-platform-tests[LayoutNG] Correct LayoutText::LinesBoundingBox() for vertical-rl. NG needs to produce a rectangle with the block-axis offset relatively to block-start of the container, just like legacy does. Using purely physical coordinates is wrong. This fixes issues with scroll anchoring, and possibly other things too. One test had to be rebaselined, due to a rounding change. LayoutText::DebugRect() calls LinesBoundingBox(), which now flips the block-axis coordinate for vertical-rl. This affects rounding of the size of the rectangle. Bug: 889449 Change-Id: I7053ed7fe05ce443f53a128660d60f27fea7f8b3 Cq-Include-Trybots: luci.chromium.try​:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1264596 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#597541} -- wpt-commits: 698d3553c23008550c9a68b196154e97ce2ed7d8 wpt-pr: 13388
e8201978a4abad1f4c8606ddad2b53d8cc2dc8ea: Bug 1497166 [wpt PR 13417] - Ignore "runner_teardown" messages in `TestRunnerManager.cleanup()`, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:41 +0000 - rev 441038
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497166 [wpt PR 13417] - Ignore "runner_teardown" messages in `TestRunnerManager.cleanup()`, a=testonly Automatic update from web-platform-testsIgnore "runner_teardown" messages in `TestRunnerManager.cleanup()` This is an alternative to https://github.com/web-platform-tests/wpt/pull/13409, which adds more handling around this rather than removing it. Fixes https://github.com/web-platform-tests/wpt/issues/13407. -- wpt-commits: 300f8e2c89abc98917b40e95c14f2edf1d354f99 wpt-pr: 13417
97dedc2880cb23bf939a685ea1cfd41cb1a32806: Bug 1497085 [wpt PR 13412] - Move a comment in TestRunnerManager.wait_finished to make more sense, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:39 +0000 - rev 441037
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497085 [wpt PR 13412] - Move a comment in TestRunnerManager.wait_finished to make more sense, a=testonly Automatic update from web-platform-testsMove a comment in TestRunnerManager.wait_finished to make more sense It's certaintly not the logging that does post-stop processing, but `after_test_end` might, so the comment is accurate if moved. The comment was added in commit 7f422ef4b1b1ecf09ff7ffc94b60c6b7bf7a41b4. -- wpt-commits: a9653ad56e60b988a38262de21c0f92b5eb13183 wpt-pr: 13412
a0482419c5d35ee353c0ffb288c30f8ba6ee6423: Bug 1497052 [wpt PR 13408] - Improve warnings of command left in queue in TestRunnerManager cleanup, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:37 +0000 - rev 441036
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497052 [wpt PR 13408] - Improve warnings of command left in queue in TestRunnerManager cleanup, a=testonly Automatic update from web-platform-testsImprove warnings of command left in queue in TestRunnerManager cleanup Part of https://github.com/web-platform-tests/wpt/issues/13407. -- Rename TestManager to TestRunnerManager in documentation/logging (There is no TestManager class.) -- Normalize messages around TestRunner/Manager more -- Fix Thread-TestRunner misnomer -- Drop the Thread-/Process- prefixes for thread/process names -- wpt-commits: a772507179527a9b2837b5f6798b41a81f9e0969, 2f50699d3942b302bd64e2ec6ce0fc9e25f62dd5, 5e4669247907398d8017e7b6539bab1041c3e4f2, d30010ae297f1057e168f360f292bb809f288bec, af795eb39d35dfb1f50c36618732995c500ef80b wpt-pr: 13408
ddb8b080f0b435ea622b4a01bee5cc0c6e12058d: Bug 1496085 [wpt PR 13334] - [css-properties-values-api] Proper behavior for direct CSSStyleValues., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Thu, 11 Oct 2018 09:31:35 +0000 - rev 441035
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496085 [wpt PR 13334] - [css-properties-values-api] Proper behavior for direct CSSStyleValues., a=testonly Automatic update from web-platform-tests[css-properties-values-api] Proper behavior for direct CSSStyleValues. In CSS Typed OM, types that are not yet supported by a specialized CSSStyleValue subclass are represented by "direct" CSSStyleValue objects. These objects are only valid for their associated property. For instance, you may not get a (direct) CSSStyleValue object from 'color', and then set it on 'background-color'; the (direct) CSSStyleValue acquired from 'color' is valid for 'color' only. The same should apply for registered custom properties; a direct CSSStyleValue acquired from '--x' is only valid for '--x'. To do this, blink::CSSUnsupportedStyleValue must be aware of the custom property name. This means the AtomicString with the custom property name must be passed around to almost everything. However, if the property at hand is not a custom property, I want to avoid AtomicString-ing the name of the property. Hence there are DCHECKs to make sure this is avoided. Reminder: this CL would be much less ... grotesque and perhaps less error-prone if dynamic CSSProperties (Ribbon) were in place, but because we like pain, we decided to not give that project a very high priority. R=chrishtr@chromium.org Bug: 641877 Change-Id: I99af4745d1d33365759e9fd4acef5082ab213229 Reviewed-on: https://chromium-review.googlesource.com/c/1257916 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#597503} -- wpt-commits: 1cefac0f876828632d234eb55f42579365664f3d wpt-pr: 13334
5100c6c46f28bbafc299040ca39708da6041c872: Bug 1486883 [wpt PR 12726] - [test_driver] Add WebDriver-style actions support, a=testonly
Navid Zolghadr <nzolghadr@chromium.org> - Thu, 11 Oct 2018 09:31:33 +0000 - rev 441034
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1486883 [wpt PR 12726] - [test_driver] Add WebDriver-style actions support, a=testonly Automatic update from web-platform-testsAdd action sequence injection in test_driver Following web driver spec for pointer action sequence and key actions this change adds this API to the test_driver interface. Use action_sequence instead of pointer_action_sequence -- [testdriver] Support sending actions sequences over WebDriver -- [testdriver] Add a builder object for constructing actions Action sequences are not really sensible to construct by hand, so this adds a builder object for constructing sequences of actions. To use it the following script mut be included after testdriver.js: <script src="/resources/testdriver-actions.js"></script> Then actions sequences can be constructed like // Drag the mouse from 0,0 to 100,100 with ctrl held down test_driver.Actions() .pointerMove(0, 0, origin="viewport") .keyDown("\uE009") .pointerDown() .pointerMove(100, 100, origin="viewport") .pointerUp() .keyUp() .send(); -- Fix error handling for testdriver tests. Otherwise a protocol error leads to FAIL not ERROR. -- Add element_by_selector to SelectorProtocolPart -- wpt-commits: ceadf71f63047e88dddd9308fd9f06db24ecfb29, f1db6b22cf40d6b56665225dfd4f83bbddd76686, 01dfc0f42edacd529749fcf543e16431ba7a9490, 723dcaffe979639976dee773c09eb24694625c23, a9504407fb46702dbb2bba7df9d349d8eba7ce55 wpt-pr: 12726
9feefc4d63b2edb086ac4f3fb49338aa8fc07b97: Bug 1496824 [wpt PR 13367] - Refactor the testharness/testdriver messaging protocol implementation, a=testonly
jgraham <james@hoppipolla.co.uk> - Thu, 11 Oct 2018 09:31:31 +0000 - rev 441033
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496824 [wpt PR 13367] - Refactor the testharness/testdriver messaging protocol implementation, a=testonly Automatic update from web-platform-testsRefactor the testharness/testdriver messaging protocol implementation (#13367) This causes most of the code to be run once when the runner window is opened rather than being run on each resume. This should be a little more efficient. However the main motivation is to have a single long-lived event handler rather than having to ensure that the event handler is correctly cleaned up after each test. Previously this was not done carefully and it was possible for events from one test to affect subsequent tests. -- wpt-commits: b0d2d2da21dfd03e86c5d710c926ae7df3b9f0d0 wpt-pr: 13367
50023456d99683f78270df0e8f5c54e772d08216: Bug 1497068 [wpt PR 13410] - Typo: runder → under, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:29 +0000 - rev 441032
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497068 [wpt PR 13410] - Typo: runder → under, a=testonly Automatic update from web-platform-testsTypo: runder → under -- wpt-commits: e0a939b563d9bb58efd3e3f70ac373104544a5c0 wpt-pr: 13410
5ea03aea88463dd69bd1dfd838b6aee1506d89dc: Bug 1497008 [wpt PR 13405] - Fix assert for StorageEvent constructor test, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:23 +0000 - rev 441031
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1497008 [wpt PR 13405] - Fix assert for StorageEvent constructor test, a=testonly Automatic update from web-platform-testsFix assert for StorageEvent constructor test (#13405) Reported by @Zirro: https://github.com/web-platform-tests/wpt/pull/13368/files/56c3da3f1c6921a9a80433657d49b42bd8c05596#r223192022 -- wpt-commits: ba4ca501a5ebdee8cbfc006bf9e7e44231b188d1 wpt-pr: 13405
113102643432c772f228e02246a2f7d606abe725: Bug 1496889 [wpt PR 13403] - Minimize <video> dependency in `test_driver.bless` test, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:22 +0000 - rev 441030
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496889 [wpt PR 13403] - Minimize <video> dependency in `test_driver.bless` test, a=testonly Automatic update from web-platform-testsMinimize <video> dependency in `test_driver.bless` test (#13403) See diagnosis of Safari Technology Preview failure: https://github.com/web-platform-tests/wpt/issues/12621#issuecomment-427525317 This test does not need to load any media resource or consider the state of the returned promise. -- wpt-commits: 21c33fe4cc3963faa4b38ab19e47660fa72c122f wpt-pr: 13403
b963411533d980a9ab8115d401f44fe590c2caee: Bug 1496891 [wpt PR 13404] - cc Update messages.json, a=testonly
Michael[tm] Smith <mike@w3.org> - Thu, 11 Oct 2018 09:31:20 +0000 - rev 441029
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496891 [wpt PR 13404] - cc Update messages.json, a=testonly Automatic update from web-platform-testscc Update messages.json -- wpt-commits: c2b30ef30749b6a8f2cc832761dfe011e63d5e94 wpt-pr: 13404
6d4ab386a8639ac055a96ebc4b6e56a4323bb1dc: Bug 1496735 [wpt PR 13368] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 08 Oct 2018 20:47:56 +0000 - rev 441028
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496735 [wpt PR 13368] - Update wpt metadata, a=testonly wpt-pr: 13368 wpt-type: metadata
e726946c50a836304adcf437ca93290e061e2a71: Bug 1496735 [wpt PR 13368] - Test StorageEvent constructor and initStorageEvent(), a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 11 Oct 2018 09:31:15 +0000 - rev 441027
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496735 [wpt PR 13368] - Test StorageEvent constructor and initStorageEvent(), a=testonly Automatic update from web-platform-testsTest initStorageEvent() Follows https://github.com/whatwg/html/pull/4063. -- Consolidate/simplify StorageEvent constructor tests The use of `async_test` was already unnecessary as `dispatchEvent` synchronously invokes listeners, and use of `dispatcEvent` itself is not necessary to test the constructor, so simplify to just `test`s. -- wpt-commits: c4fce5c3c37e30b192a596c4dc779e4192f1bc12, bd5f3403f34f8e83eecbdc172cd330039e12ab86 wpt-pr: 13368
e9a34a40b5ed39b0a88dc1e2705cfa3682a1956d: Bug 1496874 [wpt PR 13402] - cc Add some eol newlines to a couple files, a=testonly
Michael[tm] Smith <mike@w3.org> - Thu, 11 Oct 2018 09:31:13 +0000 - rev 441026
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496874 [wpt PR 13402] - cc Add some eol newlines to a couple files, a=testonly Automatic update from web-platform-testscc Add some eol newlines to a couple files -- wpt-commits: f159b42cd54c529b6e3af8222d639c68423b6283 wpt-pr: 13402
c8098d6a8df2712260e25984e801f09a9da5f45f: Bug 1496151 [wpt PR 13340] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 04 Oct 2018 01:47:09 +0000 - rev 441025
Push 34842 by aciure@mozilla.com at Sat, 13 Oct 2018 09:36:47 +0000
Bug 1496151 [wpt PR 13340] - Update wpt metadata, a=testonly wpt-pr: 13340 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip