d7b6d67aaf7cfef54c46e9d1c80872e9dd1b2da7: Bug 1483666 [wpt PR 12508] - [css-logical] Allow CSS logical shorthands to be serialized in inline and computed styles, a=testonly
Oriol Brufau <obrufau@igalia.com> - Mon, 20 Aug 2018 22:11:38 +0000 - rev 432676
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483666 [wpt PR 12508] - [css-logical] Allow CSS logical shorthands to be serialized in inline and computed styles, a=testonly Automatic update from web-platform-tests[css-logical] Allow CSS logical shorthands to be serialized in inline and computed styles Spec: https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-getpropertyvalue BUG=873760 TEST=external/wpt/css/css-logical/logical-box-border-color.html TEST=external/wpt/css/css-logical/logical-box-border-shorthands.html TEST=external/wpt/css/css-logical/logical-box-border-style.html TEST=external/wpt/css/css-logical/logical-box-border-width.html TEST=external/wpt/css/css-logical/logical-box-inset.html TEST=external/wpt/css/css-logical/logical-box-margin.html TEST=external/wpt/css/css-logical/logical-box-padding.html Change-Id: I60fca339c419d1d19eb6b31f0426c11f9d1cf95f Reviewed-on: https://chromium-review.googlesource.com/1176084 Reviewed-by: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Anders Ruud <andruud@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#584027} -- wpt-commits: 9c650fc212cdbba6ee0830a68d3af3e708e031de wpt-pr: 12508
0131ba65ffa252c739de0a8bb55fe5dc282eaf02: Bug 1484154 [wpt PR 12544] - Support CSSStyleValues in StylePropertyMap.set. (Reland), a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 20 Aug 2018 22:11:18 +0000 - rev 432675
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1484154 [wpt PR 12544] - Support CSSStyleValues in StylePropertyMap.set. (Reland), a=testonly Automatic update from web-platform-testsSupport CSSStyleValues in StylePropertyMap.set. (Reland) In StyleValueToCSSValue, when checking whether a certain CSSStyleValue matches the property in question, we now ask the registration (via CSSOMTypes) if the CSSStyleValue matches. If it doesn't match, we throw a TypeError like for normal properties. If it does match, the CSSStyleValue is stringified, tokenized, and set on the style rule as tokens. I have postponed support for <color> and <transform-function>, because CSSUnsupportedStyleValue currently does not handle registered custom properties at all. This is appropriate to fix in a separate CL. Note that, because the string version of StylePropertyMap.set also uses StyleValueToCSSValue, it will no longer be possible to set registered custom properties with a string--even if the syntax is matched. A subsequent CL will fix this. R=futhark@chromium.org Bug: 641877 Change-Id: Ib5c31640f81e957620339c9bdf617ab1af5d3d47 Reviewed-on: https://chromium-review.googlesource.com/1179153 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#584024} -- wpt-commits: b6f1c190818648dc0c33eb7ada54bf3f209fc938 wpt-pr: 12544
b7174f9d6e6437c09f9b70c2d89a980034db11b8: Bug 1484150 [wpt PR 12543] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 17 Aug 2018 08:06:37 +0000 - rev 432674
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1484150 [wpt PR 12543] - Update wpt metadata, a=testonly wpt-pr: 12543 wpt-type: metadata
21ea0e12a53b371949816fc94232f99163c15026: Bug 1484150 [wpt PR 12543] - Fix cookie prefix tests., a=testonly
Mike West <mkwst@chromium.org> - Mon, 20 Aug 2018 22:10:59 +0000 - rev 432673
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1484150 [wpt PR 12543] - Fix cookie prefix tests., a=testonly Automatic update from web-platform-testsFix cookie prefix tests. The layout tests aren't testing much at the moment, as they're never served over HTTPS. This patch creates `.https` versions of the tests and reworks them to actually exercise the behavior of `__Host` and `__Secure` cookie prefixes. Bug: 843945 Change-Id: I31968133ca8846f3ffc4faec2339e3d0d03c77f8 Reviewed-on: https://chromium-review.googlesource.com/1179150 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#584016} -- wpt-commits: 4205ee12965bea420482d4d08cbac00b44cbad90 wpt-pr: 12543
a8490f20070e459fc74075f155e06ea96eb8e280: Bug 1483994 [wpt PR 12535] - Revert "Cache Storage: Check for duplicate entries in Cache.addAll().", a=testonly
Ben Kelly <wanderview@chromium.org> - Mon, 20 Aug 2018 22:10:42 +0000 - rev 432672
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483994 [wpt PR 12535] - Revert "Cache Storage: Check for duplicate entries in Cache.addAll().", a=testonly Automatic update from web-platform-testsRevert "Cache Storage: Check for duplicate entries in Cache.addAll()." This reverts commit 74fd352e51322e823070088c7d5c72e911966580. Reason for revert: Moving behind experimental feature flag until web compat can be assessed. Original change's description: > Cache Storage: Check for duplicate entries in Cache.addAll(). > > This implements step 4.2.3 of the BatchCacheOperations algorithm: > > https://w3c.github.io/ServiceWorker/#batch-cache-operations-algorithm > > Bug: 720919 > Change-Id: I679f786441b813ed816a183522021c417f4ab7b8 > Reviewed-on: https://chromium-review.googlesource.com/1162362 > Commit-Queue: Ben Kelly <wanderview@chromium.org> > Reviewed-by: Joshua Bell <jsbell@chromium.org> > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > Reviewed-by: Victor Costan <pwnall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#582738} TBR=jsbell@chromium.org,kinuko@chromium.org,pwnall@chromium.org,wanderview@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 720919 Change-Id: I08736e4ec638a65c48f329966f378698a6d9b045 Reviewed-on: https://chromium-review.googlesource.com/1178502 Reviewed-by: Victor Costan <pwnall@chromium.org> Commit-Queue: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#583849} -- wpt-commits: 2dda7b8c10c7566fa6167a32b09c85d51baf2a85 wpt-pr: 12535
d37a2b5f7caaf336b2810df7aa2c397bad3dbb3f: Bug 1482457 [wpt PR 12413] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 16 Aug 2018 21:50:35 +0000 - rev 432671
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1482457 [wpt PR 12413] - Update wpt metadata, a=testonly wpt-pr: 12413 wpt-type: metadata
c068c3396e147d00d16b5cb6430e54026fa59d1c: Bug 1482457 [wpt PR 12413] - Implement ignore-opens-during-unload counter in Document, a=testonly
Timothy Gu <timothygu@chromium.org> - Mon, 20 Aug 2018 22:10:23 +0000 - rev 432670
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1482457 [wpt PR 12413] - Implement ignore-opens-during-unload counter in Document, a=testonly Automatic update from web-platform-testsImplement ignore-opens-during-unload counter in Document The removed test fast/loader/document-destruction-within-unload.html was originally added in 8809405d796cf3023e26cefd4b06f369eb67f125, to make sure that a document.write() call that blows away the current page still works in unload event listeners and blocks any current attempt to navigate. Since we no longer allow that to happen, the test is obsolete. In fact, it can be seen as contradictory to external/wpt/html/browsers/browsing-the-web/unloading-documents/005.html, which tests that document.open() in an unload event doesn't block navigation. Bug: 583586, 866274 Change-Id: I99b35dd28c97e8603455805b31d49644bc7b23a5 Reviewed-on: https://chromium-review.googlesource.com/1169320 Commit-Queue: Timothy Gu <timothygu@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#583836} -- wpt-commits: d44f0f56d5d7d5d4b9e50be0ad2c4331f81c7bf7 wpt-pr: 12413
e3ab676a310dc46b40d08a29166c02611085d3cf: Bug 1483770 [wpt PR 12512] - [css-grid] Distribution offset doesn't account for non-spanning items, a=testonly
Javier Fernandez <jfernandez@igalia.com> - Mon, 20 Aug 2018 22:10:06 +0000 - rev 432669
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483770 [wpt PR 12512] - [css-grid] Distribution offset doesn't account for non-spanning items, a=testonly Automatic update from web-platform-tests[css-grid] Distribution offset doesn't account for non-spanning items We recenttly changed the track sizing algorithm so that it considers the offsets added by the Content Alignment properties. The change in r566412 introduce intermediate steps in the track sizing algorithm so that inline-axis Content Distribution accounts for the row tracks sizes computed in the next step. However, we were adding the Content Distribution offsets for any column track, but we should do it only for the tracks with spanning items. This error led to the mentioned bugs and this change fixes them. Bug: 871230, 871242 Change-Id: I8ac789ccacc2e5a51bfafd7820ed08e96a31e58b Reviewed-on: https://chromium-review.googlesource.com/1176803 Reviewed-by: Sergio Villar <svillar@igalia.com> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#583802} -- wpt-commits: 676265b89417b09c27d94a2a8538a88a34821e88 wpt-pr: 12512
74bdd33d51f170168cfd0e8be456ebb298cd0ebc: Bug 1484002 [wpt PR 12537] - Remove the Budget API tests, a=testonly
Peter Beverloo <peter@lvp-media.com> - Mon, 20 Aug 2018 22:09:49 +0000 - rev 432668
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1484002 [wpt PR 12537] - Remove the Budget API tests, a=testonly Automatic update from web-platform-testsRemove the Budget API tests (#12537) The specification has been made obsolete with no existing implementations. We can revive these tests from history if that changes. https://wicg.github.io/budget-api/ -- wpt-commits: d617cdbf1278785ebcfd949be18231b7fc0eebed wpt-pr: 12537
d267941739e09595fc8343a0e365290aed1c1740: Bug 1483997 [wpt PR 12536] - Revert "[css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set.", a=testonly
Xida Chen <xidachen@chromium.org> - Mon, 20 Aug 2018 22:09:32 +0000 - rev 432667
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483997 [wpt PR 12536] - Revert "[css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set.", a=testonly Automatic update from web-platform-testsRevert "[css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set." This reverts commit b786c57cab4e93f6736fecfcc986c36dfbddd507. Reason for revert: <INSERT REASONING HERE> layout test failed: https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20ASAN/15210 Original change's description: > [css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set. > > In StyleValueToCSSValue, when checking whether a certain CSSStyleValue > matches the property in question, we now ask the registration (via > CSSOMTypes) if the CSSStyleValue matches. If it doesn't match, we throw > a TypeError like for normal properties. If it does match, the CSSStyleValue > is stringified, tokenized, and set on the style rule as tokens. > > I have postponed support for <color> and <transform-function>, because > CSSUnsupportedStyleValue currently does not handle registered custom > properties at all. This is appropriate to fix in a separate CL. > > Note that, because the string version of StylePropertyMap.set also uses > StyleValueToCSSValue, it will no longer be possible to set registered > custom properties with a string--even if the syntax is matched. > A subsequent CL will fix this. > > R=​futhark@chromium.org > > Bug: 641877 > Change-Id: Ie0cc2f87e39f8f59015824bfd1b81efaf402c326 > Reviewed-on: https://chromium-review.googlesource.com/1175822 > Commit-Queue: Anders Ruud <andruud@chromium.org> > Reviewed-by: Rune Lillesveen <futhark@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583695} TBR=futhark@chromium.org,andruud@chromium.org Change-Id: I2486be60ce81497253bdf64903ea870832a0ef9e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 641877 Reviewed-on: https://chromium-review.googlesource.com/1178503 Reviewed-by: Xida Chen <xidachen@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#583747} -- wpt-commits: 5e22f7526ccd18de75184a12dc835cc23d3ea0be wpt-pr: 12536
41966d1c0faad97fcbe0b6909fc05a9ca0e5b944: Bug 1483989 [wpt PR 12533] - Re-enable the Background Fetch WPT tests, a=testonly
Peter Beverloo <peter@chromium.org> - Mon, 20 Aug 2018 22:09:16 +0000 - rev 432666
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483989 [wpt PR 12533] - Re-enable the Background Fetch WPT tests, a=testonly Automatic update from web-platform-testsRe-enable the Background Fetch WPT tests The flaky crashes should have been fixed now that the associated logic has been removed from the scheduler. https://chromium-review.googlesource.com/c/chromium/src/+/1165554 Bug: 869470, 869818 Change-Id: Ie077876289a28387e5f890e9a25abe5609857c14 Reviewed-on: https://chromium-review.googlesource.com/1170909 Commit-Queue: Peter Beverloo <peter@chromium.org> Reviewed-by: Rayan Kanso <rayankans@chromium.org> Reviewed-by: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#583729} -- wpt-commits: f4cfe41feec71829ec58aa0bf8ef3b8bf489dc7f wpt-pr: 12533
f6749ea61079f8633a21bf2b178927e6b7ab9b65: Bug 1483991 [wpt PR 12534] - Sync Mozilla tests as of 2018-08-16, a=testonly
L. David Baron <dbaron@dbaron.org> - Mon, 20 Aug 2018 22:08:58 +0000 - rev 432665
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483991 [wpt PR 12534] - Sync Mozilla tests as of 2018-08-16, a=testonly Automatic update from web-platform-testsSync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/4248cea4f9a1e5cb64c0d121ff248e11e003e9e2 . (#12534) This contains a single change, from [Bug 1472843](https://bugzilla.mozilla.org/show_bug.cgi?id=1472843) by @iyermihir, reviewed by @dholbert. -- wpt-commits: 507d63bba2e1d3aee550f161498f396ff4ab6842 wpt-pr: 12534
d07641a80a1f4d91a8f85f1acd2e0366197bc620: Bug 1483570 [wpt PR 12503] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 15 Aug 2018 17:20:40 +0000 - rev 432664
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483570 [wpt PR 12503] - Update wpt metadata, a=testonly wpt-pr: 12503 wpt-type: metadata
3166f55901c15bab16166a1daa2ebe09c4395311: Bug 1483570 [wpt PR 12503] - [css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 20 Aug 2018 22:08:38 +0000 - rev 432663
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1483570 [wpt PR 12503] - [css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set., a=testonly Automatic update from web-platform-tests[css-properties-values-api] Support CSSStyleValues in StylePropertyMap.set. In StyleValueToCSSValue, when checking whether a certain CSSStyleValue matches the property in question, we now ask the registration (via CSSOMTypes) if the CSSStyleValue matches. If it doesn't match, we throw a TypeError like for normal properties. If it does match, the CSSStyleValue is stringified, tokenized, and set on the style rule as tokens. I have postponed support for <color> and <transform-function>, because CSSUnsupportedStyleValue currently does not handle registered custom properties at all. This is appropriate to fix in a separate CL. Note that, because the string version of StylePropertyMap.set also uses StyleValueToCSSValue, it will no longer be possible to set registered custom properties with a string--even if the syntax is matched. A subsequent CL will fix this. R=futhark@chromium.org Bug: 641877 Change-Id: Ie0cc2f87e39f8f59015824bfd1b81efaf402c326 Reviewed-on: https://chromium-review.googlesource.com/1175822 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#583695} -- wpt-commits: 218a15f938b8612bac6a74baa8cccdaf53d57221 wpt-pr: 12503
2dcc5b1e23dde5ef5ed30c1f38e40b149aa00744: Bug 1460859 [wpt PR 10963] - Add basic text in a shape tests., a=testonly
Chris Lilley <chris@w3.org> - Mon, 20 Aug 2018 22:08:20 +0000 - rev 432662
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1460859 [wpt PR 10963] - Add basic text in a shape tests., a=testonly Automatic update from web-platform-testsMerge pull request #10963 from Tavmjong/text-shape Add basic text in a shape tests. -- wpt-commits: 79d77b7a845d6a141feeb7f2f719fa121b34be89 wpt-pr: 10963
3446e763cf522ae6165a9e693b301a04dc904764: Bug 1460043 [wpt PR 7633] - css generated content: added test for counter-* calc() values, a=testonly
Chris Lilley <chris@w3.org> - Mon, 20 Aug 2018 22:07:58 +0000 - rev 432661
Push 106829 by wptsync@mozilla.com at Tue, 21 Aug 2018 21:06:34 +0000
Bug 1460043 [wpt PR 7633] - css generated content: added test for counter-* calc() values, a=testonly Automatic update from web-platform-testsMerge pull request #7633 from ondras/counter-calc css generated content: added test for counter-* calc() values -- wpt-commits: c1b66fc2e065d2045d258111aa4d28f9395cdb8e wpt-pr: 7633
4cd236eff0af42029e5ff209e46c9384aa2c9c3c: Bug 1471743 - remove STRICT_FAKE_SYMLINKS code from nsLocalFileWin; r=erahm
Nathan Froyd <froydnj@mozilla.com> - Tue, 21 Aug 2018 17:00:59 -0400 - rev 432660
Push 106828 by nfroyd@mozilla.com at Tue, 21 Aug 2018 21:01:14 +0000
Bug 1471743 - remove STRICT_FAKE_SYMLINKS code from nsLocalFileWin; r=erahm We don't define STRICT_FAKE_SYMLINKS anywhere, so this is dead code.
9f92f288b60876c75fddfddb2eba8ff685ed2b78: Bug 1484420 - Move locale-related functions into js/public/LocaleSensitive.h that isn't #include'd in jsapi.h. r=anba
Jeff Walden <jwalden@mit.edu> - Mon, 20 Aug 2018 17:11:32 -0500 - rev 432659
Push 106827 by jwalden@mit.edu at Tue, 21 Aug 2018 20:33:18 +0000
Bug 1484420 - Move locale-related functions into js/public/LocaleSensitive.h that isn't #include'd in jsapi.h. r=anba
3c5aa35fa3d2674821a481ee46e67805b2e6b057: Bug 1483245 - Add telemetry probes for amount of time spent on paint thread and the amount of tasks. r=jrmuizel
Ryan Hunt <rhunt@eqrion.net> - Fri, 17 Aug 2018 15:22:34 -0500 - rev 432658
Push 106826 by rhunt@eqrion.net at Tue, 21 Aug 2018 20:32:35 +0000
Bug 1483245 - Add telemetry probes for amount of time spent on paint thread and the amount of tasks. r=jrmuizel
4841b3ddbacbb80dfd48c5c0b9737d6c33c7bcaa: Bug 1483772 - Never have mAsyncTask be non-null when we cannot paint. r=nical
Ryan Hunt <rhunt@eqrion.net> - Thu, 16 Aug 2018 10:33:14 -0500 - rev 432657
Push 106826 by rhunt@eqrion.net at Tue, 21 Aug 2018 20:32:35 +0000
Bug 1483772 - Never have mAsyncTask be non-null when we cannot paint. r=nical In bug 1482415 a special check was added for the case where we fail to allocate a buffer and started an async task. This papered over one crash for another as ClientPaintedLayer also assumes that if there is an async task there is a capture. It'd be best to just null out mAsyncTask and keep those checks as is. Differential Revision: https://phabricator.services.mozilla.com/D3520
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip