a46c08092f37ff84190acaa8c08f30b3ab09a709: Bug 1494049 [wpt PR 13201] - Add headless mode for chrome_webdriver, a=testonly
Geoffrey Sneddon <me@gsnedders.com> - Fri, 28 Sep 2018 09:54:17 +0000 - rev 438716
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1494049 [wpt PR 13201] - Add headless mode for chrome_webdriver, a=testonly Automatic update from web-platform-testsAdd headless mode for chrome_webdriver (#13201) 0200c63a74a540dfb870881d5f476280c367d1c1 failed to add this to chrome_webdriver, so add this now. -- wpt-commits: 1e7408fcd394b66234c38c24ba044ec6f00e4b70 wpt-pr: 13201
eecc27b7ef231fa3f30fdee9fde57129e8b85638: Bug 1493748 [wpt PR 13193] - [css-properties-values-api] Substitution behavior., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Fri, 28 Sep 2018 09:54:15 +0000 - rev 438715
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493748 [wpt PR 13193] - [css-properties-values-api] Substitution behavior., a=testonly Automatic update from web-platform-tests[css-properties-values-api] Substitution behavior. Currently, registered properties substitute into other values exactly like specified (like unregistered properties). This means that, for a <length>-registered property with a specified value "10em" (for instance), when that property is substituted via var()-reference, the tokens "10em" are inserted. This is not correct, and produces the wrong result with e.g. inherited values. This CL changes that, by implementing "absolutization" of registered custom properties: a process which calculates the computed value of the property, and then produces a token stream usable for substitution which is equivalent to the computed value. * Currently we resolve var()-references on all custom properties before applying high-priority properties. This is no longer possible, because the true value of a custom property (also unregistered) can not be known until the font has been updated. Consider: --reg-len: 1em; --unreg:var(--reg-len). Here, the computed value of --unreg should be "16px" (assuming a font-size of 16px), and not "1em". If we destructively resolve --unreg before the font size is known, we end up with the wrong tokens. Hence the resolution process has been moved to after the font has been updated. * Custom properties must also be usable from high-priority properties. Since they are no longer resolved beforehand, they are resolved "on the fly", non-destructively. "Non-destructively" means that resolved token streams are not stored on ComputedStyle, such that any var()-references are kept for the _real_ resolution pass after the font has been updated. This works, because the high-priority properties do not require proper "absolute substitution" to produce the correct value. Note that font-size is special, in that font-relative units may not be used if they arrive via a registered custom property. * There is a special resolving pass for registered custom properties (ComputeRegisteredVariables). This pass produces non-absolute CSSValues for calculation of animation. * Parsing of registered properties now happens entirely in CSSVariableResolver, and no longer in variable.cc. Having this in multiple places is just confusing. R=futhark@chromium.org Bug: 641877 Change-Id: Ic705d0808ffcea0ae5db02fb20870767175bb706 Reviewed-on: https://chromium-review.googlesource.com/1240274 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#593902} -- wpt-commits: c801e269e3e22d11e1bb4530ff15e87db877b1d2 wpt-pr: 13193
8ded955398d6da9e9a534e2e983d6583439be3b8: Bug 1493651 [wpt PR 13185] - Fix firefox find_binary_path to accomodate channels, a=testonly
Ahilya Sinha <ahilyasinha99@gmail.com> - Fri, 28 Sep 2018 09:54:13 +0000 - rev 438714
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493651 [wpt PR 13185] - Fix firefox find_binary_path to accomodate channels, a=testonly Automatic update from web-platform-testsFix firefox find_binary_path to accomodate channels Firefox find_binary_path returned None since browser-channels were introduced due to path differences. This fixes the same, along with a minor change to the Nightly path on Mac as it contains a space. The default for |wpt run firefox| without a channel specified is set to nightly, along with a log message when this happens. -- wpt-commits: f3a1f9324097311cafcd7893066e3e40fe172fd0 wpt-pr: 13185
8144d7627b787613dcfb81a1fe754d97bf8d8ad7: Bug 1493432 [wpt PR 13168] - Add interface tests for TransitionEvent, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Fri, 28 Sep 2018 09:54:11 +0000 - rev 438713
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493432 [wpt PR 13168] - Add interface tests for TransitionEvent, a=testonly Automatic update from web-platform-testsAdd interface tests for TransitionEvent These are modelled after the similar tests that exist for AnimationEvent in css/css-animations, except written using more modern WPT style. Bug: 695504 Change-Id: I63573cf48aba6821f5e22486ef18217d0f2828ee Reviewed-on: https://chromium-review.googlesource.com/1239457 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Xida Chen <xidachen@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#593620} -- wpt-commits: b040cb2a07264d35b9f47cd9deb2fb2889fca6d4 wpt-pr: 13168
2ee6cf2cb1dc314a59594fc4e63123607f0248cf: Bug 1493382 [wpt PR 13157] - [PE] Fix fragment clip and paint offset under multicol vertical-rl scrolled, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Fri, 28 Sep 2018 09:54:09 +0000 - rev 438712
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493382 [wpt PR 13157] - [PE] Fix fragment clip and paint offset under multicol vertical-rl scrolled, a=testonly Automatic update from web-platform-tests[PE] Fix fragment clip and paint offset under multicol vertical-rl scrolled The previous code in VisualOffsetFromPaintOffsetRoot() converting the result into scrolling contents space used ScrolledContentOffset which mismatched the new ScrollTranslation which also includes scroll origin. Now use ScrollTranslation instead. Also removed the wrong remedy about scroll origin in one of the callers. Bug: 887423 Cq-Include-Trybots: luci.chromium.try​:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I9a72ed6ddc066c5b4c9970037ed4c4287c5a2f0f Reviewed-on: https://chromium-review.googlesource.com/1239170 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#593572} -- wpt-commits: 68d63d516e6bc4b83934d71616b2aa82d8efe2af wpt-pr: 13157
557a989b9ef788d50008720c20e5423086fe3ac9: Bug 1488291 [wpt PR 12816] - [css-grid] Performance optimizations in the Baseline alignment code, a=testonly
Javier Fernandez <jfernandez@igalia.com> - Fri, 28 Sep 2018 09:54:07 +0000 - rev 438711
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1488291 [wpt PR 12816] - [css-grid] Performance optimizations in the Baseline alignment code, a=testonly Automatic update from web-platform-tests[css-grid] Performance optimizations in the Baseline alignment code Since we integrated the baseline alignment logic in the grid tracks sizing algorithm, its impact on performance has grown considerably. The analysis of the new logic added and its overhead, due to different operations, shows that evaluating the item's participation in the baseline alignment context is the most expensive one. It's specially demanding the evaluation of the grid item's alignment properties. Considering that currently we are doing this for every grid item, this CL propose to reuse the loop we already have to clear the grid item's override size to cache the items with a baseline value in their alignment CSS properties. Thanks to this cache we can determine the item's participation in a baseline alignment context in the different phases of the track sizing algorithm, with almost no cost (compared to the current logic). It may be possible to share the cache with the algorithm run for computing the grid's intrinsic size; however, if the intrinsic size logic is run before the grid's layout, we'll end up duplicating the cache. Additionally, this cache is also used in the alignment phase of the grid layout logic; this change helps to avoid the various issues we have been suffering related to the different evaluations of the item's participation in baseline during the different phases of the grid layout algorithm. BUG = 873452 Change-Id: Ida27be11ae0f5c455e6077367a277981ab35cec1 Reviewed-on: https://chromium-review.googlesource.com/1179897 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#593552} -- wpt-commits: f6de5f7d5d50b1ad30a1e17922e183868fd3e935 wpt-pr: 12816
725e07fa06ebf57387781bd20104439e35b82e19: Bug 1492493 [wpt PR 13076] - Add a headless mode command line option, a=testonly
jgraham <james@hoppipolla.co.uk> - Fri, 28 Sep 2018 09:54:05 +0000 - rev 438710
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1492493 [wpt PR 13076] - Add a headless mode command line option, a=testonly Automatic update from web-platform-testsAdd a headless mode command line option (#13076) For browsers which support headless mode starting wptrunner with --headless will run the tests in headless mode; otherwise it will be ignored. --no-headless is avaiable to explicitly disable the mode when frontends change the defaults. For firefox switch the default for wpt run to be headless; for Chrome changing the default broke some smoketests, so don't switch until that is resolved. In all cases continue to run in a normal windowed mode in CI. -- wpt-commits: 0200c63a74a540dfb870881d5f476280c367d1c1 wpt-pr: 13076
54c47d6ca05acb6f5497aff26fa8d01153584169: Bug 1493657 [wpt PR 13187] - Visual change on background-clip changes., a=testonly
Rune Lillesveen <futhark@chromium.org> - Fri, 28 Sep 2018 09:54:04 +0000 - rev 438709
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493657 [wpt PR 13187] - Visual change on background-clip changes., a=testonly Automatic update from web-platform-testsVisual change on background-clip changes. The background-clip property affects background-color visually, so we need to say a layer is visually different even without an image. We had a wpt test for this which had a stray line which made the test always pass. Bug: 887350 Change-Id: Icc585f9e631485970b6509e015eff1e2007e4f0b Reviewed-on: https://chromium-review.googlesource.com/1238448 Reviewed-by: Anders Ruud <andruud@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#593523} -- wpt-commits: 00c1fd9ea4bc1e03f966919f1e209ab8cd81f57e wpt-pr: 13187
2c74b71ebcf3625340c0563a007bacc595c98750: Bug 1472773 [wpt PR 11757] - Fix some tests in test_request.py for python 3., a=testonly
Ms2ger <Ms2ger@gmail.com> - Fri, 28 Sep 2018 09:54:02 +0000 - rev 438708
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1472773 [wpt PR 11757] - Fix some tests in test_request.py for python 3., a=testonly Automatic update from web-platform-testsFix some tests in test_request.py for python 3. (#11757) -- wpt-commits: 61e09bec3d21b4e9137dadafc20c04cb9be7ce3e wpt-pr: 11757
d32687beccaefe1ce8edb48d3156c0d2775915d0: Bug 1493424 [wpt PR 13167] - Update mozrunner to 7.0.2, a=testonly
pyup.io bot <github-bot@pyup.io> - Fri, 28 Sep 2018 09:54:00 +0000 - rev 438707
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493424 [wpt PR 13167] - Update mozrunner to 7.0.2, a=testonly Automatic update from web-platform-testsUpdate mozrunner from 7.0.0 to 7.0.2 (#13167) -- wpt-commits: 91491deb7dcfe4a0d0ece61f086345abad4d46a4 wpt-pr: 13167
490377bcd48954e7142534085c9577b48b0b90fc: Bug 1493663 [wpt PR 13188] - Typo: seperated → separated, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 27 Sep 2018 19:57:19 +0000 - rev 438706
Push 108384 by wptsync@mozilla.com at Fri, 28 Sep 2018 15:48:17 +0000
Bug 1493663 [wpt PR 13188] - Typo: seperated → separated, a=testonly Automatic update from web-platform-testsTypo: seperated → separated (#13188) Found by https://chromium-review.googlesource.com/c/chromium/src/+/1240181#message-2a9347bd8ccd79130eb02de97600c0faf4d429ce But the same typo also made elsewhere. -- wpt-commits: 75a06f907589cab45d901e88b54babb182e2446f wpt-pr: 13188
0707d19d36be4057d1982f62a5adcf4a8f525433: Merge mozilla-central to inbound. a=merge CLOSED TREE
Tiberius Oros <toros@mozilla.com> - Fri, 28 Sep 2018 18:42:23 +0300 - rev 438705
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Merge mozilla-central to inbound. a=merge CLOSED TREE
156f9442db847c065c50af78968226369f47c151: Merge inbound to mozilla-central. a=merge
Tiberius Oros <toros@mozilla.com> - Fri, 28 Sep 2018 18:39:03 +0300 - rev 438704
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Merge inbound to mozilla-central. a=merge
1ba2376aa7fcec04e0c240d4512700ea0bfd68b7: Bug 1459720 - Move the performance panel out of the toolbox to the WebIDE's top level window r=jdescottes
Julien Wajsberg <felash@gmail.com> - Fri, 28 Sep 2018 12:48:05 +0000 - rev 438703
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Bug 1459720 - Move the performance panel out of the toolbox to the WebIDE's top level window r=jdescottes This effectively removes the devtools overhead while profiling... as long as the toolbox isn't opened as well of course. This also removes the performance panel from the Browser Toolbox and the Browser Content Toolbox where it shouldn't have been in the first place. Differential Revision: https://phabricator.services.mozilla.com/D6904
9eec82950e697b92227f63804879c055d8471cf2: Bug 1494316 - Update generated json and moz.build files; r=dmajor
Dan Minor <dminor@mozilla.com> - Thu, 27 Sep 2018 17:39:12 +0000 - rev 438702
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Bug 1494316 - Update generated json and moz.build files; r=dmajor Depends on D7102 Differential Revision: https://phabricator.services.mozilla.com/D7104
5120c3c3f28cb758e2c731f78d86c432e6e8ead2: Bug 1494316 - Remove gn generated json files for win64; r=dmajor
Dan Minor <dminor@mozilla.com> - Thu, 27 Sep 2018 17:41:31 +0000 - rev 438701
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Bug 1494316 - Remove gn generated json files for win64; r=dmajor These are identical to the 32 bit versions and so are no longer necessary to correctly generate moz.build files for windows. Depends on D7101 Differential Revision: https://phabricator.services.mozilla.com/D7102
b2ef383204c5af98c56a525a9b0287a29fc1c591: Bug 1494316 - Set enable_iterator_debugging; r=dmajor
Dan Minor <dminor@mozilla.com> - Thu, 27 Sep 2018 17:41:34 +0000 - rev 438700
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Bug 1494316 - Set enable_iterator_debugging; r=dmajor This flag is not required and causes problems with mingw builds. Differential Revision: https://phabricator.services.mozilla.com/D7101
98eabe8273c12207e45d60a65d960b42604100d8: Merge mozilla-central to autoland. a=merge CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Fri, 28 Sep 2018 14:53:09 +0300 - rev 438699
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
f30d81ec891f23f6ec2cdb99f3adb023d4e8957f: Backed out changeset 7a8e2093a124 (bug 1494639) for inheritance.sub.html failures CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Fri, 28 Sep 2018 14:47:31 +0300 - rev 438698
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Backed out changeset 7a8e2093a124 (bug 1494639) for inheritance.sub.html failures CLOSED TREE
7a8e2093a12411219a2c25a0c70610b07516952d: Bug 1494639 - Ensure that css test doesn't try to contact an external host r=emilio
James Graham <james@hoppipolla.co.uk> - Fri, 28 Sep 2018 10:31:55 +0000 - rev 438697
Push 108383 by toros@mozilla.com at Fri, 28 Sep 2018 15:42:52 +0000
Bug 1494639 - Ensure that css test doesn't try to contact an external host r=emilio Differential Revision: https://phabricator.services.mozilla.com/D7164
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip