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

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

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

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

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

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

Bug 1483570 [wpt PR 12503] - Update wpt metadata, a=testonly wpt-pr: 12503 wpt-type: metadata

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

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

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

Bug 1471743 - remove STRICT_FAKE_SYMLINKS code from nsLocalFileWin; r=erahm We don't define STRICT_FAKE_SYMLINKS anywhere, so this is dead code.

Bug 1484420 - Move locale-related functions into js/public/LocaleSensitive.h that isn't #include'd in jsapi.h. r=anba

Bug 1483245 - Add telemetry probes for amount of time spent on paint thread and the amount of tasks. r=jrmuizel

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

Bug 1485114 - Avoid creating nsPermission objects in the permission manager needlessly; r=nika

Bug 1485099 - Add some logging to the AntiTracking component for the saving and reading of storage access permissions; r=smaug

Bug 1484848 - Remove the XPCOM component registrations for window and child window; r=mstange

Backed out 2 changesets (bug 1484420) for hazard failures on a CLOSED TREE Backed out changeset d910e3c8372a (bug 1484420) Backed out changeset d79cdb73c55f (bug 1484420)

Bug 1484420 - Add a missing #include needed only in builds that aren't --with-intl-api. r=bustage in a CLOSED TREE

Bug 1484420 - Move locale-related functions into js/public/LocaleSensitive.h that isn't #include'd in jsapi.h. r=anba