Set the "network.trr.disable-ECS" pref to false to disable.
MozReview-Commit-ID: GE6L8Vpvuu0
Differential Revision: https://phabricator.services.mozilla.com/D2933
--HG--
extra : moz-landing-system : lando
We can now simply call setInputValue and the autocompletion
will happen. Since we are forcing the call to jsterm.complete,
there were 2 calls made to the server, making the measurements
in the test erroneous.
This also revealed a race in setInputValue: the text was
set by codeMirror before the cursor was actually moved. Which
means we were sending an erroneous autocompletion query to the
server.
We use codeMirror.operation to tell codeMirror to both set the
text and the cursor in a single operation.
Differential Revision: https://phabricator.services.mozilla.com/D3192
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsMerge pull request #10926 from Tavmjong/markers-orient
Add test for marker 'orient' attribute.
--
wpt-commits: eea0b54014e970a2f94f1c35ec6e18ece76beb76
wpt-pr: 10926
Automatic update from web-platform-testsMerge pull request #10275 from dstorey/svgaelement-additions
Add tests for rel, rellist, download, and text on SVGAElement
--
wpt-commits: 60f5bae752dd625ae83a730c635254cdb9f3d970
wpt-pr: 10275
Automatic update from web-platform-testsMerge pull request #10249 from dstorey/svg-document-element-events
Add test for DocumentAndElementEventHandlers in SVG
--
wpt-commits: 1529e32ac8073c48e872e7d705a10daa24decbbf
wpt-pr: 10249
Automatic update from web-platform-testsUse a .worker.js test for WorkerGlobalScope_requestAnimationFrame.
--
wpt-commits: 5a3a984492dcd1b1586576790922baf0a208dfb5
wpt-pr: 12293
Automatic update from web-platform-tests[LayoutNG] Pass constraint space to inline children for min/max.
Orthogonal flow root children are going to need to calculate an
extrinsic constraint space. We already got this right for direct block
children, but not for floated children of inline child nodes.
Three tests start to pass, but I wrote a new test as well, that's more
to the point (it used to fail a DCHECK, and then render incorrectly, if
we bypassed that).
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Iffea4e8cb26f41f8b5caac4bbb7185df5f62f7d7
Reviewed-on: https://chromium-review.googlesource.com/1162175
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581188}
--
wpt-commits: 25475a3887220baee22dfef032474040401d84e3
wpt-pr: 12297
Automatic update from web-platform-tests[css-grid] Change how percentage row tracks and gaps are resolved
The CSSWG decided to change how percentage row tracks and gutters
in a grid container with indefinite height are resolved.
The CSSWG issues are:
* https://github.com/w3c/csswg-drafts/issues/1921
* https://github.com/w3c/csswg-drafts/issues/509
So far they were resolved as "auto", like it happens with
percentage heights in regular blocks. But now they're going to behave
similar to what happens in the columns axis, they would be ignored
to compute the intrinsic height.
This causes that we need to repeat the track sizing algorithm
when we have a grid container with indefinite height
that has some percentage rows using the intrinsic height
calculated on the first pass. Then the percentages will be resolved
against the intrinsic height.
We are adding two new tests for this new behavior
on top of updating several tests that were using percentages.
We also add a test for content alignment and the second pass
when the row size changes, the last case fails due to crbug.com/871230.
JFTR, intent to implement and ship thread:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/CJgcT4hR7Rk/58WfZNbWBQAJ
BUG=846187
TEST=css/css-grid/grid-definition/grid-percentage-rows-indefinite-height-001.html
TEST=css/css-grid/grid-definition/grid-percentage-rows-indefinite-height-002.html
TEST=css/css-grid/alignment/grid-content-alignment-second-pass-002.html
Change-Id: I2a1959af6c95e0c47d294580599fdbf9bc432348
Reviewed-on: https://chromium-review.googlesource.com/1142409
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Cr-Commit-Position: refs/heads/master@{#581185}
--
wpt-commits: 244c6baf38953eac29840e2fbcb8a42dd8bafe88
wpt-pr: 12089
Automatic update from web-platform-testsMerge pull request #10926 from Tavmjong/markers-orient
Add test for marker 'orient' attribute.
--
wpt-commits: eea0b54014e970a2f94f1c35ec6e18ece76beb76
wpt-pr: 10926
Automatic update from web-platform-testsMerge pull request #10275 from dstorey/svgaelement-additions
Add tests for rel, rellist, download, and text on SVGAElement
--
wpt-commits: 60f5bae752dd625ae83a730c635254cdb9f3d970
wpt-pr: 10275
Automatic update from web-platform-testsMerge pull request #10249 from dstorey/svg-document-element-events
Add test for DocumentAndElementEventHandlers in SVG
--
wpt-commits: 1529e32ac8073c48e872e7d705a10daa24decbbf
wpt-pr: 10249
Automatic update from web-platform-testsUse a .worker.js test for WorkerGlobalScope_requestAnimationFrame.
--
wpt-commits: 5a3a984492dcd1b1586576790922baf0a208dfb5
wpt-pr: 12293
Automatic update from web-platform-tests[LayoutNG] Pass constraint space to inline children for min/max.
Orthogonal flow root children are going to need to calculate an
extrinsic constraint space. We already got this right for direct block
children, but not for floated children of inline child nodes.
Three tests start to pass, but I wrote a new test as well, that's more
to the point (it used to fail a DCHECK, and then render incorrectly, if
we bypassed that).
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Iffea4e8cb26f41f8b5caac4bbb7185df5f62f7d7
Reviewed-on: https://chromium-review.googlesource.com/1162175
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581188}
--
wpt-commits: 25475a3887220baee22dfef032474040401d84e3
wpt-pr: 12297
Automatic update from web-platform-tests[css-grid] Change how percentage row tracks and gaps are resolved
The CSSWG decided to change how percentage row tracks and gutters
in a grid container with indefinite height are resolved.
The CSSWG issues are:
* https://github.com/w3c/csswg-drafts/issues/1921
* https://github.com/w3c/csswg-drafts/issues/509
So far they were resolved as "auto", like it happens with
percentage heights in regular blocks. But now they're going to behave
similar to what happens in the columns axis, they would be ignored
to compute the intrinsic height.
This causes that we need to repeat the track sizing algorithm
when we have a grid container with indefinite height
that has some percentage rows using the intrinsic height
calculated on the first pass. Then the percentages will be resolved
against the intrinsic height.
We are adding two new tests for this new behavior
on top of updating several tests that were using percentages.
We also add a test for content alignment and the second pass
when the row size changes, the last case fails due to crbug.com/871230.
JFTR, intent to implement and ship thread:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/CJgcT4hR7Rk/58WfZNbWBQAJ
BUG=846187
TEST=css/css-grid/grid-definition/grid-percentage-rows-indefinite-height-001.html
TEST=css/css-grid/grid-definition/grid-percentage-rows-indefinite-height-002.html
TEST=css/css-grid/alignment/grid-content-alignment-second-pass-002.html
Change-Id: I2a1959af6c95e0c47d294580599fdbf9bc432348
Reviewed-on: https://chromium-review.googlesource.com/1142409
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Cr-Commit-Position: refs/heads/master@{#581185}
--
wpt-commits: 244c6baf38953eac29840e2fbcb8a42dd8bafe88
wpt-pr: 12089
