3716a1d0c0c110e1cfe801429e001f59d80cce77: Bug 1509137 [wpt PR 14168] - CSS: WPTs for various computed values, a=testonly
Eric Willigers <ericwilligers@chromium.org> - Tue, 27 Nov 2018 20:12:08 +0000 - rev 505159
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1509137 [wpt PR 14168] - CSS: WPTs for various computed values, a=testonly Automatic update from web-platform-testsCSS: WPTs for various computed values Test computed values for various properties from - css-animations - css-shapes - css-transitions - css-ui - css-writing-modes - filter-effects Change-Id: Iad28fe2030f922bdcaa80d6ade383c69106b8822 Reviewed-on: https://chromium-review.googlesource.com/c/1345955 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#610240} -- wpt-commits: 48071530dab0ba974375debca0ad7c7033b00c49 wpt-pr: 14168
f95c3eb84ad6fe9b33766df8ff54a1580f67aa89: Bug 1509211 [wpt PR 14173] - [LayoutNG] Rebaseline quirky test that actually passes., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Tue, 27 Nov 2018 20:12:06 +0000 - rev 505158
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1509211 [wpt PR 14173] - [LayoutNG] Rebaseline quirky test that actually passes., a=testonly Automatic update from web-platform-tests[LayoutNG] Rebaseline quirky test that actually passes. (writing-mode has nothing to do with it, FWIW) Legacy layout is buggy here, so the expected rendering was wrong. Also wrote a new wpt test for this. When calculating quirky line height, the legacy engine makes room for whitespace that is to be collapsed. Bug: 845902 Change-Id: I004d024578bb147d4f70c58fc1e3213a14174fd7 Reviewed-on: https://chromium-review.googlesource.com/c/1346465 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#610216} -- wpt-commits: f5a1cc435d35fbe72fd29f89ecea9fdc8168bec7 wpt-pr: 14173
48ab9c0a88dd621d6ab0bbecd20746943a6383dc: Bug 1508904 [wpt PR 14152] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 22 Nov 2018 14:35:17 +0000 - rev 505157
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1508904 [wpt PR 14152] - Update wpt metadata, a=testonly wpt-pr: 14152 wpt-type: metadata
e93fd4f50dd100d515cc84b92832b9e9fa5889bc: Bug 1508904 [wpt PR 14152] - IndexedDB: Handle the opaque origin case for IDBFactory.databases(), a=testonly
Andreas Butler <andreasbutler@google.com> - Tue, 27 Nov 2018 20:12:01 +0000 - rev 505156
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1508904 [wpt PR 14152] - IndexedDB: Handle the opaque origin case for IDBFactory.databases(), a=testonly Automatic update from web-platform-testsIndexedDB: Handle the opaque origin case for IDBFactory.databases() Implemented the proper throwing behaviour for handling the case of an opaque origin for IDBFactory.databases(). Also included is a WPT for verifying the behaviour written by jsbell@. Spec PR: https://github.com/w3c/IndexedDB/pull/250 Change-Id: I506f82bf69b27d34b499eacbe12aaa18a69b63be Reviewed-on: https://chromium-review.googlesource.com/c/1344629 Commit-Queue: Andreas Butler <andreasbutler@google.com> Reviewed-by: Joshua Bell <jsbell@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#610143} -- wpt-commits: 909109663818a4abe194324356208644d5602ddc wpt-pr: 14152
33848f48c13677e4deaf92fbf734ef925e0da8bb: Bug 1507627 [wpt PR 14081] - Replace general source type with none source type, a=testonly
Navid Zolghadr <nzolghadr@chromium.org> - Tue, 27 Nov 2018 20:11:58 +0000 - rev 505155
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1507627 [wpt PR 14081] - Replace general source type with none source type, a=testonly Automatic update from web-platform-testsReplace general source type with none source type (#14081) * Replace general source type with none source type Based on the web driver spec the general source type string should be "none". https://w3c.github.io/webdriver/#input-source-state * Add a test * Rename the test title, move to promise test, set expectation for Chrome -- wpt-commits: c6d4a3c8d42294787a54c9667675873c224e3e1a wpt-pr: 14081
dad19f5060770ae8e9d5042b8e218a25fd49a5f8: Bug 1508060 [wpt PR 14114] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 22 Nov 2018 17:11:15 +0000 - rev 505154
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1508060 [wpt PR 14114] - Update wpt metadata, a=testonly wpt-pr: 14114 wpt-type: metadata
0818f88fb0cfb9216e37e2556fe85446e3e388e8: Bug 1508060 [wpt PR 14114] - SVG Painting: property parsing, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Tue, 27 Nov 2018 20:11:53 +0000 - rev 505153
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1508060 [wpt PR 14114] - SVG Painting: property parsing, a=testonly Automatic update from web-platform-testsSVG Painting: property parsing (#14114) Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity https://github.com/w3c/svgwg/issues/403#issuecomment-439600770 Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' https://github.com/w3c/svgwg/issues/592 Browsers accept numeric stroke-dashoffset and stroke-width https://github.com/w3c/svgwg/issues/534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/ -- wpt-commits: e50224228f7629af05d08a50f36afbacfbd0158e wpt-pr: 14114
71695efab9bf510ec99feb06410c64ece414ff9f: Bug 1509097 [wpt PR 14164] - Update interfaces/mediasession.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 27 Nov 2018 20:11:50 +0000 - rev 505152
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1509097 [wpt PR 14164] - Update interfaces/mediasession.idl, a=testonly Automatic update from web-platform-testsUpdate interfaces/mediasession.idl (#14164) Source: https://github.com/tidoust/reffy-reports/blob/740515b/whatwg/idl/mediasession.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/457811203 -- wpt-commits: b448498ebda2f3cf2e8d8ce66a93603096c51e4e wpt-pr: 14164
408677f045b29f5aedb53f27d14eed5908b06519: Merge mozilla-central to mozilla-inbound. a=merge on a CLOSED TREE
Daniel Varga <dvarga@mozilla.com> - Thu, 29 Nov 2018 12:02:09 +0200 - rev 505151
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Merge mozilla-central to mozilla-inbound. a=merge on a CLOSED TREE
df022f193cb4b6d8f87504223adc2a2f8789be31: Bug 1510247. Fix some unified build issues in widget code. r=spohl
Jonathan Watt <jwatt@jwatt.org> - Wed, 14 Nov 2018 17:03:36 +0000 - rev 505150
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1510247. Fix some unified build issues in widget code. r=spohl Differential Revision: https://phabricator.services.mozilla.com/D13061
85dab0b936897a3ce5d7f96bdd2a1c92bc0a8500: Bug 1510422 - Fix autocomplete cache handling; r=Honza.
Nicolas Chevobbe <nchevobbe@mozilla.com> - Thu, 29 Nov 2018 13:58:57 +0000 - rev 505149
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1510422 - Fix autocomplete cache handling; r=Honza. In Bug 1462394, we moved the autocomplete data handling out of the JsTerm to the Redux store. In the process, we regress some cases like `await n`, which should display `navigator`, but isn't anymore when the user types the whole sequence. Ctrl+Space would still show the popup, which indicates that the issue is not on the server-side. This issue is caused because our new code decides that we should hit the cache when typing the `n`, and there's nothing in the cache. Previously, we were clearing the cache as soon as the input last string wasn't alphanumeric, which we don't anymore. To fix that, instead of relying on the last string of the input (which could be wrong in cases like `x.["hello `), we clear the cache when the autocomplete service returns a null `matches` property. In the JsPropertyProvider, we use to return null whenever there isn't any search done (incorrect input, empty match prop, …). So it seems like a good idea to bust the cache when the server returns null. This requires some changes to the autocomplete service, as well as some in jsPropertyProvider (e.g. to handle `await `). Tests are added both on the client and the frontend to make sure we don't regress this (those tests fail without the actual fix). Differential Revision: https://phabricator.services.mozilla.com/D13231
6c5424f777093578ce457708056e2f0d72c6b5e4: No Bug, mozilla-central repo-update HSTS HPKP blocklist remote-settings - a=repo-update r=RyanVM
ffxbld <ffxbld@mozilla.com> - Thu, 29 Nov 2018 13:37:25 +0000 - rev 505148
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
No Bug, mozilla-central repo-update HSTS HPKP blocklist remote-settings - a=repo-update r=RyanVM Differential Revision: https://phabricator.services.mozilla.com/D13388
8ea04ec01e9905d4714aa01ade891d552c56a3a6: Bug 1497552 - Remove support for 44100 Hz in dtmf_tone_generator; r=padenot
Dan Minor <dminor@mozilla.com> - Thu, 29 Nov 2018 12:59:01 +0000 - rev 505147
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1497552 - Remove support for 44100 Hz in dtmf_tone_generator; r=padenot Assertions in NetEqImpl::SetSampleRateAndChannels prevent us from requesting tones at 44100 Hz, so this code can be safely removed. Differential Revision: https://phabricator.services.mozilla.com/D12982
eb07312cfbe868780ebed84fc83e5a5470e81fb4: Bug 1497602 - Enable DirectX screen capturer on Windows; r=pehrsons
Dan Minor <dminor@mozilla.com> - Thu, 29 Nov 2018 13:27:23 +0000 - rev 505146
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1497602 - Enable DirectX screen capturer on Windows; r=pehrsons This enables support for the DirectX screen capturer. We use the default DesktopCaptureOptions which do not set the option to use the DirectX screen capturer so this change will have no effect with the current code. For what it's worth, I tested enabling the DirectX option and it worked fine on my system, but I don't see any reason to not follow the defaults provided by webrtc.org in this case. Differential Revision: https://phabricator.services.mozilla.com/D13303
eff4ffb1d280a3dc97b330d876d72542ee2ee32d: Bug 1502462 - The altSrv checker does not build a uri correctly if origin is ipv6 address. r=valentin
Dragana Damjanovic <dd.mozilla@gmail.com> - Thu, 29 Nov 2018 10:15:13 +0000 - rev 505145
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1502462 - The altSrv checker does not build a uri correctly if origin is ipv6 address. r=valentin AltSvcMapping::ProcessHeader should use GetAsciiHost instead of GetHost. Differential Revision: https://phabricator.services.mozilla.com/D13066
952e4606a7c9334cc0213396e7b63faa414a20f1: Bug 1510948 - Fix ObjectInspector arrows styling in console; r=Honza.
Nicolas Chevobbe <nchevobbe@mozilla.com> - Thu, 29 Nov 2018 12:49:24 +0000 - rev 505144
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1510948 - Fix ObjectInspector arrows styling in console; r=Honza. Differential Revision: https://phabricator.services.mozilla.com/D13381
e593d06bcd929ab543824921434def8c6e4c6c5b: Bug 1510862 - Prevent exponential blowup of custom properties. r=jwatt
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 29 Nov 2018 10:16:38 +0000 - rev 505143
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1510862 - Prevent exponential blowup of custom properties. r=jwatt Put a hard cap on the value length instead of counting substitutions, because it works best, see the comment. Differential Revision: https://phabricator.services.mozilla.com/D13352
e5dd0884d82f63374310093d48dc12ad7cf726c8: Backed out changeset 3e5ea9da2cbb (bug 1510862) for Linting failure. CLOSED TREE
Dorel Luca <dluca@mozilla.com> - Thu, 29 Nov 2018 12:35:42 +0200 - rev 505142
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Backed out changeset 3e5ea9da2cbb (bug 1510862) for Linting failure. CLOSED TREE
04f0bbf40bf36957dc1f72a8aae9916df0e3222f: Bug 1508472 - Part 5: Fifth batch of comment fix-ups in preparation for the tree reformat r=sylvestre
Ehsan Akhgari <ehsan@mozilla.com> - Thu, 29 Nov 2018 10:30:46 +0000 - rev 505141
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1508472 - Part 5: Fifth batch of comment fix-ups in preparation for the tree reformat r=sylvestre This is a best effort attempt at ensuring that the adverse impact of reformatting the entire tree over the comments would be minimal. I've used a combination of strategies including disabling of formatting, some manual formatting and some changes to formatting to work around some clang-format limitations. Differential Revision: https://phabricator.services.mozilla.com/D13371
3e5ea9da2cbbb0e9ac5d27a277f921ca9d470c85: Bug 1510862 - Prevent exponential blowup of custom properties. r=jwatt
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 29 Nov 2018 10:16:38 +0000 - rev 505140
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1510862 - Prevent exponential blowup of custom properties. r=jwatt Put a hard cap on the value length instead of counting substitutions, because it works best, see the comment. Differential Revision: https://phabricator.services.mozilla.com/D13352
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip