bd099c6fb9cf627af469bbdfd74ff77da43a5bbc: Bug 1454380 [wpt PR 8508] - Test that requestMediaKeySystemAccess sets label, a=testonly
theodab <theodab@google.com> - Sun, 22 Apr 2018 15:11:15 +0000 - rev 415277
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1454380 [wpt PR 8508] - Test that requestMediaKeySystemAccess sets label, a=testonly Automatic update from web-platform-testsTest that requestMediaKeySystemAccess sets label (#8508) On Edge, navigator.requestMediaKeySystemAccess ignores the value passed along to the label configuration field. This test exposes that bug. See https://goo.gl/6SgCRb -- wpt-commits: e6cffaa6d307ec6ef08102aad9c7a4a1df5b7d53 wpt-pr: 8508
4bbea84414ab0ea6b8abfc02c682c9e6c02e647e: Bug 1453792 [wpt PR 10454] - Make PointerEvent fromElement/toElement return null., a=testonly
Mustaq Ahmed <mustaq@google.com> - Sun, 22 Apr 2018 15:09:57 +0000 - rev 415276
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453792 [wpt PR 10454] - Make PointerEvent fromElement/toElement return null., a=testonly Automatic update from web-platform-testsMake PointerEvent fromElement/toElement return null. Also added web-platform-tests. Blink intent thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/G2s1Ol3qcgA Closes https://github.com/w3c/pointerevents/issues/167 Bug: 827271 Change-Id: I8429b9541f8cfc38223b3a34116b74c2aba92ee5 Reviewed-on: https://chromium-review.googlesource.com/986877 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#550683} -- wpt-commits: 81bcc8db4c676828d4b33ccb90c94049ffd831cf wpt-pr: 10454
2e40cf6fa01c585aedfb5e71c9a0233126f8a159: Bug 1454039 [wpt PR 10463] - Revert "Reland: Use PostTask to schedule cross-process postMessage forwarding.", a=testonly
Ben Pastene <bpastene@chromium.org> - Sun, 22 Apr 2018 15:08:40 +0000 - rev 415275
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1454039 [wpt PR 10463] - Revert "Reland: Use PostTask to schedule cross-process postMessage forwarding.", a=testonly Automatic update from web-platform-testsRevert "Reland: Use PostTask to schedule cross-process postMessage forwarding." This reverts commit 7c3d1d13f940e88ef6706fd8b5c257a81d340ed9. Reason for revert: WebviewLoginTest.Basic is still flaky on linux-chromeos-rel https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6886 https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6887 Original change's description: > Reland: Use PostTask to schedule cross-process postMessage forwarding. > > Changes from original attempt at https://crrev.com/c/999182: > - fix flakiness in two additional ChromeOS login tests > - fix CSP WPT tests to not depend on ordering between iframe's onload > and postMessage - see https://crbug.com/832319. > > Previously, we sent the IPC to forward a cross-process postMessage > immediately. This caused a behavioral difference from the > same-process case where the postMessage is always scheduled. Namely, > in a scenario like this: > > frame.postMessage(...); > doSomethingThatSendsIPCsToFrame(frame); > > the IPCs from JS following the postMessage would've been ordered > incorrectly, causing |frame| to see their side effects after the > postMessage dispatch in the cross-process case, whereas they would be > seen before the postMessage dispatch in the same-process case. One > example of this is frame.focus(), and another is a frame element > onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after > a postMessage dispatched from an inline script while the frame was > still loading. > > To resolve these ordering concerns, this CL changes cross-process > postMessage to do a PostTask on the sender side before sending the > message to the browser process. This improves the current state of > the world, but does not yet achieve a perfect match for the IPC > ordering in the same-process case - see discussion on the bug. > > Bug: 828529 > Change-Id: I62a627c501526d09900be4f5bd2c899acf4d1e07 > Reviewed-on: https://chromium-review.googlesource.com/999182 > Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Commit-Queue: Alex Moshchuk <alexmos@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#550284} > Reviewed-on: https://chromium-review.googlesource.com/1011287 > Cr-Commit-Position: refs/heads/master@{#550621} TBR=xiyuan@chromium.org,dcheng@chromium.org,alexmos@chromium.org Change-Id: Ic0637a6038bed6e5334a26e1934bee81faad3b9e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 828529 Reviewed-on: https://chromium-review.googlesource.com/1012138 Reviewed-by: Ben Pastene <bpastene@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#550649} -- wpt-commits: 6ad1b51de7dce0d45d08cc0f47a92a7b1fed69d2 wpt-pr: 10463
5a85849690304374b25e7d7b30d4dd77b0c8dc3c: Bug 1450522 [wpt PR 10263] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 01 Apr 2018 03:04:06 +0000 - rev 415274
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1450522 [wpt PR 10263] - Update wpt metadata, a=testonly wpt-pr: 10263 wpt-type: metadata
8469c16d69c5ac2b1e050428bfb571d7e53753d7: Bug 1450522 [wpt PR 10263] - Update serialization of timing functions, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Sun, 22 Apr 2018 15:07:14 +0000 - rev 415273
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1450522 [wpt PR 10263] - Update serialization of timing functions, a=testonly Automatic update from web-platform-testsMerge pull request #10263 from csnardi/patch-10 Update serialization of timing functions -- wpt-commits: 7b20d124d59d8d0e3e5b2f9da594e7b4aa1bcb1e wpt-pr: 10263
60ed7d758b1b4f5afaa636416cf3b5568316ca5e: Bug 1452989 [wpt PR 10399] - Web Animations: Fix bugs in procedure to process a keyframes argument, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Sun, 22 Apr 2018 15:05:57 +0000 - rev 415272
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1452989 [wpt PR 10399] - Web Animations: Fix bugs in procedure to process a keyframes argument, a=testonly Automatic update from web-platform-testsWeb Animations: Fix bugs in procedure to process a keyframes argument There were three minor bugs left in the implementation: - We threw on lists-in-custom-iterators instead of just ignoring them. - We returned all properties on the keyframe rather than just those defined on the keyframe itself (e.g. we would include prototype properties, against spec). - We didn't access the properties in ascending unicode order. Bug: 827573 Change-Id: I213ae5b24e1f35d7f28d16625025122950a6ba88 Reviewed-on: https://chromium-review.googlesource.com/989261 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#550641} -- wpt-commits: 2707869d65f3a4d5a1f2ab1d44920b19695a7cde wpt-pr: 10399
b5a7874d1f31011fc3ffc401ad16a05f546edb8d: Bug 1455843 [wpt PR 10462] - Accept variation in serialization of 'background', a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Sun, 22 Apr 2018 15:04:40 +0000 - rev 415271
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1455843 [wpt PR 10462] - Accept variation in serialization of 'background', a=testonly Automatic update from web-platform-testsMerge pull request #10462 from ewilligers/background-serialization-variety Accept variation in serialization of 'background' -- wpt-commits: 1e5a5fefe15c4fcc1a3267daf1d75598f736c82f wpt-pr: 10462
8fee71d393903989b19422c2b592236e6806d9e0: Bug 1453952 [wpt PR 10456] - Reland: Use PostTask to schedule cross-process postMessage forwarding., a=testonly
Alex Moshchuk <alexmos@chromium.org> - Sun, 22 Apr 2018 15:03:24 +0000 - rev 415270
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453952 [wpt PR 10456] - Reland: Use PostTask to schedule cross-process postMessage forwarding., a=testonly Automatic update from web-platform-testsReland: Use PostTask to schedule cross-process postMessage forwarding. Changes from original attempt at https://crrev.com/c/999182: - fix flakiness in two additional ChromeOS login tests - fix CSP WPT tests to not depend on ordering between iframe's onload and postMessage - see https://crbug.com/832319. Previously, we sent the IPC to forward a cross-process postMessage immediately. This caused a behavioral difference from the same-process case where the postMessage is always scheduled. Namely, in a scenario like this: frame.postMessage(...); doSomethingThatSendsIPCsToFrame(frame); the IPCs from JS following the postMessage would've been ordered incorrectly, causing |frame| to see their side effects after the postMessage dispatch in the cross-process case, whereas they would be seen before the postMessage dispatch in the same-process case. One example of this is frame.focus(), and another is a frame element onload event (dispatched via FrameHostMsg_DispatchLoad) arriving after a postMessage dispatched from an inline script while the frame was still loading. To resolve these ordering concerns, this CL changes cross-process postMessage to do a PostTask on the sender side before sending the message to the browser process. This improves the current state of the world, but does not yet achieve a perfect match for the IPC ordering in the same-process case - see discussion on the bug. Bug: 828529 Change-Id: I62a627c501526d09900be4f5bd2c899acf4d1e07 Reviewed-on: https://chromium-review.googlesource.com/999182 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#550284} Reviewed-on: https://chromium-review.googlesource.com/1011287 Cr-Commit-Position: refs/heads/master@{#550621} -- wpt-commits: f281334c36847064b75740239882e2684aee0437 wpt-pr: 10456
846bc7887b927295a8c7d2f51f5e486394171970: Bug 1446406 [wpt PR 10076] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 17 Apr 2018 15:01:10 +0000 - rev 415269
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1446406 [wpt PR 10076] - Update wpt metadata, a=testonly wpt-pr: 10076 wpt-type: metadata
a5e3429241aa802c67decfa3b6b1f54db2f7a11b: Bug 1446406 [wpt PR 10076] - Allow feature policy to be used in opaque origins., a=testonly
Ian Clelland <iclelland@chromium.org> - Sun, 22 Apr 2018 15:02:01 +0000 - rev 415268
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1446406 [wpt PR 10076] - Allow feature policy to be used in opaque origins., a=testonly Automatic update from web-platform-testsAllow feature policy to be used in opaque origins. Currently, policy-controlled features do not work as expected in frames with opaque origins, such as isolated sandboxes and data: URLs, because the eventual opaque origin of the frame is not known when the HTMLFrameOwnerElement builds the container policy, and so has no way to tell the browser that a particular origin should be allowed. This CL adds a new member to the ParsedFeaturePolicyDeclaration, which indicates that the iframe policy is expected to apply to the origin of the frame, and is used when that frame has an opaque origin. This can be triggered with an iframe of the form <iframe sandbox allow="feature"> or <iframe sandbox allow="feature src"> This flag is checked when building the feature policy in the new frame, and ensures that the new feature policy will allow the feature in that origin. This is the first part of the eventual solution -- currently this has the effect of allowing the feature even if a sandboxed frame navigates to a new page (causing a new opaque origin to be created for it). Subsequent CLs will add a unique identified to each such origin, and ensure that the generated policies are properly tied to the specific origin of the frame. Bug: 690520 Change-Id: Ie18b9bc3c36be6550baf5a03e355871b9589fd40 Reviewed-on: https://chromium-review.googlesource.com/963382 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#550463} -- wpt-commits: 4c8580c189ce4501997af80b599bea070b1a7299 wpt-pr: 10076
705bd1cb7b3fab5b8f53a92f400c4e488aff9193: Bug 1452840 [wpt PR 10390] - [css-typed-om] Support offset-rotate., a=testonly
Darren Shen <shend@chromium.org> - Sun, 22 Apr 2018 15:00:37 +0000 - rev 415267
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1452840 [wpt PR 10390] - [css-typed-om] Support offset-rotate., a=testonly Automatic update from web-platform-tests[css-typed-om] Support offset-rotate. Introduces the <angle> data type. Test fails because we compute offset-rotate to a pair rather than 'as specified' had to rebaseline all the tests. Bug: 820299 Change-Id: Ifdc192550b0b544b9887af80c259b3bfeede556b Reviewed-on: https://chromium-review.googlesource.com/1003433 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#550146} -- wpt-commits: 1dd03e794199f6430072ecef144991112136cca5 wpt-pr: 10390
bf219acff879bf5b48dd41e9f8620a8da1f250ca: Bug 1453975 [wpt PR 10458] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 21 Apr 2018 14:27:01 +0000 - rev 415266
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453975 [wpt PR 10458] - Update wpt metadata, a=testonly wpt-pr: 10458 wpt-type: metadata
fd08cd58bd9311d3ed4fb84068064a856003c633: Bug 1453975 [wpt PR 10458] - Fix race in track-stats.https.html test., a=testonly
Henrik Boström <hbos@chromium.org> - Sun, 22 Apr 2018 14:59:15 +0000 - rev 415265
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453975 [wpt PR 10458] - Fix race in track-stats.https.html test., a=testonly Automatic update from web-platform-testsFix race in track-stats.https.html test. This resolves the onIceConnectionStateComplete probmise when iceConnectionState reaches either 'connected' or 'completed' and fixes the race if it had already reached these states before the function was called. This fix is speculative. I am no longer able to repro the TIMEOUT locally with or without the fix. Bug: 829401 Change-Id: I1dec90250d640d93498c59a932ab5e84a3b96f15 Reviewed-on: https://chromium-review.googlesource.com/1012029 Reviewed-by: Harald Alvestrand <hta@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#550580} -- wpt-commits: a4accccea67a4de543edebaa51aa8c8b898aa323 wpt-pr: 10458
f65230bf509558277ddedffa43e9518dcd48adef: Bug 1453442 [wpt PR 10429] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 11 Apr 2018 19:36:39 +0000 - rev 415264
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453442 [wpt PR 10429] - Update wpt metadata, a=testonly wpt-pr: 10429 wpt-type: metadata
b4c37d148d52084ef1d0c3563cc75bee1632b337: Bug 1453442 [wpt PR 10429] - [cssom] Add a test for mutation records when CSSStyleDeclaration.setPropertyValue is invoked., a=testonly
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 22 Apr 2018 14:57:44 +0000 - rev 415263
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453442 [wpt PR 10429] - [cssom] Add a test for mutation records when CSSStyleDeclaration.setPropertyValue is invoked., a=testonly Automatic update from web-platform-testsMerge pull request #10429 from emilio/mutation-record [cssom] Add a test for mutation records when CSSStyleDeclaration.setPropertyValue is invoked. -- wpt-commits: ab9fc1edc3f464617d6ed72a2336d064f9cdcfcc wpt-pr: 10429
64574b6ba265941a1ca3e1d1fbcbb058751780bf: Bug 1452841 [wpt PR 10391] - [css-typed-om] Support remaining misc properties., a=testonly
Darren Shen <shend@chromium.org> - Sun, 22 Apr 2018 14:56:27 +0000 - rev 415262
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1452841 [wpt PR 10391] - [css-typed-om] Support remaining misc properties., a=testonly Automatic update from web-platform-tests[css-typed-om] Support remaining misc properties. Known failures: - all: computed value is always "", it should compute to something... - animation-name: <custom-ident> not mentioned in typed om spec. - cursor: 'grab' and 'grabbing' are still webkit prefixed. - list-style-type: Blink implements something different to the spec. - page: computed value is always "", <custom-ident> not mentioned in typedom spec - perspective: '0' seems to compute to none. - perspective-origin: Blink doesn't support 'none' keyword - quotes: computed value is always "" - size: computed value is always "" - speak: Blink implements something different to the spec. - transform-box: Blink doesn't support 'border-box' keyword - z-index: computed value is always 'auto' (might be something to do with stacking context) Bug: 820299 Change-Id: I629dda1c4bcac92f59cae3bddf11bd375f98e5c2 Reviewed-on: https://chromium-review.googlesource.com/1003434 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#550527} -- wpt-commits: 071e621564bc4af04a04e8b8e515bfb306a6613e wpt-pr: 10391
cf6b746fb4c27da0bcd73b3e4e966c04bcb6da7e: Bug 1452883 [wpt PR 10394] - Stringify RequestInit.body, a=testonly
Yutaka Hirano <yhirano@chromium.org> - Sun, 22 Apr 2018 14:55:10 +0000 - rev 415261
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1452883 [wpt PR 10394] - Stringify RequestInit.body, a=testonly Automatic update from web-platform-testsStringify RequestInit.body As specified, RequestInit.body should be stringified, i.e., {toString(): () => 'hi!'} should be treated as same as 'hi!'. Bug: 831076 Change-Id: I4118c0faa9535d62b3db2529bf23716fdc25a997 Reviewed-on: https://chromium-review.googlesource.com/1004561 Reviewed-by: Adam Rice <ricea@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#550523} -- wpt-commits: 96bceca65945e50c61128eaf5473fc9bc9e46c99 wpt-pr: 10394
5c86d62788bf7e4f8e6f41cbddf8d207cda0ad46: Bug 1453595 [wpt PR 10440] - custom-elements: Implement customElements.upgrade()., a=testonly
Kent Tamura <tkent@chromium.org> - Sun, 22 Apr 2018 14:53:53 +0000 - rev 415260
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453595 [wpt PR 10440] - custom-elements: Implement customElements.upgrade()., a=testonly Automatic update from web-platform-testscustom-elements: Implement customElements.upgrade(). Intent-to-implement-and-ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zCQe7UkR07w Bug: 819482 Change-Id: I5645d5711d7fe1323992533e6c73593ba59d1bca Reviewed-on: https://chromium-review.googlesource.com/1009450 Reviewed-by: Hayato Ito <hayato@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#550513} -- wpt-commits: 08c935c755a5f9cc0ef8a7b9f56091e5d2b040d9 wpt-pr: 10440
35a8769bac5b0ca27802dc264da9696f1fb28f7a: Bug 1453439 [wpt PR 10434] - Remove http/tests/w3c, a=testonly
Nicolas Pena <npm@chromium.org> - Sun, 22 Apr 2018 14:52:35 +0000 - rev 415259
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453439 [wpt PR 10434] - Remove http/tests/w3c, a=testonly Automatic update from web-platform-testsRemove http/tests/w3c This CL moves the final user-timing tests to external/wpt and removes the folder. The performance_entrylist_checker is changed as in the http counterpart to allow de-duplicating test messages. There are some tests that are related to the wpt counterparts, but not equivalent and in a different format, so unifying some of these tests can be done in the future. Bug: 498037 Change-Id: I6f35d962ba088d92a9768e49a65dea4d5c267491 Reviewed-on: https://chromium-review.googlesource.com/1007888 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#550310} -- wpt-commits: 51704839c172ba8a70910bff484837c25adbfc9a wpt-pr: 10434
f8aebe28f718953583c54d81ff15f7600f17f9b8: Bug 1453641 [wpt PR 10443] - Use version-specific prefs files when running Firefox, a=testonly
jgraham <james@hoppipolla.co.uk> - Sun, 22 Apr 2018 14:51:21 +0000 - rev 415258
Push 102533 by wptsync@mozilla.com at Tue, 24 Apr 2018 12:30:46 +0000
Bug 1453641 [wpt PR 10443] - Use version-specific prefs files when running Firefox, a=testonly Automatic update from web-platform-testsUse version-specific prefs files when running Firefox (#10443) Firefox requires a prefs file to be loaded to ensure that it doesn't make external network connections, and to make sure that other settings are appropriate for testing. Previously we always used the version of the prefs file from master, which is usually fine for nightly builds, but doesn't work with release builds if it happens that a pref changed. This change uses the correct release version of the prefs file for firefox releases and beta versions. It continues to use the master version for any nightly build; this could be fixed in some cases if we are able to access the actual commit hash used to build Firefox, but probably isn't too bad an approximation. The caching algorithm was changed so that release versions of the prefs are cached forever, and the nightly version is updated once per day (although this doesn't quite match the nightly release cadence, it's only going to fail in edge cases where the prefs were changed in the file, but the nightly version was not yet updated, of vice-versa.) -- wpt-commits: cf2ef62f1c470b47a03275c795c6dedd69eace88 wpt-pr: 10443
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip