Automatic update from web-platform-testsMake sure stacking context is always updated for ::first-letter.
::first-letter sadly has at least three code paths for computing its
computed style. Two of them were lacking stacking context update. There
is work in progress for Squad to mend this, but let's fix the current
code paths for now.
Bug: 856806
Change-Id: Ifeea799643bfa266e58c948f476bc23481fcdd5e
Reviewed-on: https://chromium-review.googlesource.com/1120249
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571512}
--
wpt-commits: 02cfdfe53b794884bcd731e18f845bec59dfd707
wpt-pr: 11731
Automatic update from web-platform-testsMake sync-tests.sh work with git.
--
Allow specifying the mozilla tree via argument.
--
wpt-commits: 8b61c282650bf72bce0147df320425343ea27f2f, e639f5b4158852b16ffa28613730c2b0b63f5e83
wpt-pr: 11715
Automatic update from web-platform-testsSync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/6041c030780420b6205cf2d6640513606609884c
This contains two changes:
* One by Mihir Iyer from [bug 1398483](https://bugzil.la/1398483), reviewed by
@dholbert, adding flexbox column-{row,gap} reftests.
* One by myself from [bug 1464782](https://bugzil.la/1464782), replacing the
usage of offset-* logical properties by the standard name inset-*, reviewed
by @upsuper.
--
wpt-commits: dc302574be5e27db4ade270698c966a39a09e300
wpt-pr: 11714
Automatic update from web-platform-testsUpdate external/wpt/webrtc/RTCRtpParameters* tests.
This is in preparation for get/setParameters[1] and
RTCRtpTransceiver[2].
Tests are updated to use promise_test and async/await to make them
easier to write and to execute sequentially.
Tests are updated to set up a call before getParameters() because many
parameters are defined as "that has been negotiated". If we want to test
what is returned before negotiation we should add that as separate
tests. For now, this is necessary for the tests to run on [1][2].
Some tests are removed because they no longer reflect the spec.
Because get/setParameters() and RTCRtpTransceiver has not landed yet,
the tests are still expected to fail.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1102436
[2] https://chromium-review.googlesource.com/c/chromium/src/+/1025771
Bug: 803494, 777617
Change-Id: I3f14a37925837576a602d91bb67e48181c56a946
Reviewed-on: https://chromium-review.googlesource.com/1102502
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571430}
--
wpt-commits: 36fb033a4051e63a0ab4bd073fdaadf808953564
wpt-pr: 11526
Automatic update from web-platform-testsUpdate links to feature policy documentation.
The documentation in the Feature Policy spec repository was moved to the
'master' branch from the 'gh-pages' branch. This updates several
references in the Chromium codebase with the new locations.
TBR=kinuko
To-be-reviewed-by: kinuko@chromium.org
Bug: 857055
Change-Id: I10b4c55608a218b1767a4990832d86e460cd37d5
Reviewed-on: https://chromium-review.googlesource.com/1116868
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570906}
--
wpt-commits: d60079a316ee35415d426ed5a2e8c0574efca80c
wpt-pr: 11687
Automatic update from web-platform-testsMark a vertical-scroll test as 'slow'
The test has been previously disabled (skipped) on Windows due to
recurrent timeouts. Running the test locally leads to an average of ~
3.7 sec runtime on a high-performance Windows 10 rig (Z840). The test is
not skipped on Linux right now, but since its runtime exceeds the 2 sec
rule of thumb (from the comments in SlowTests), this CL will make it
slow on Linux as well.
Bug: 850964
Change-Id: Ib478c0f59313da4302325578d9b768e1070bdcb6
Reviewed-on: https://chromium-review.googlesource.com/1115214
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571116}
--
wpt-commits: fdc6e085458e80d3bfccfe59dc47adc7dd14bc45
wpt-pr: 11690
Automatic update from web-platform-tests[LayoutNG] bugfix for NG painting in vertical-rl with scrollbars.
This bug occurs when painting NG child inside non-inline vertical-rl parent
with scrollbars.
Root cause is extra scrollbar offset that Paint applies to Legacy painting that
is not needed for NG.
The fix is hacky: NG applies reverse offset.
This fix does not make any additional tests pass or fail.
Bug: 852395
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: I7dda2cdbf682485ab30c048987ae683981731886
Reviewed-on: https://chromium-review.googlesource.com/1115863
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571080}
--
wpt-commits: e7aa3025a97a793b4fe5776dcf616f6e845d1ce0
wpt-pr: 11703
MozReview-Commit-ID: JlUogtQDeVU
Automatic update from web-platform-tests[LayoutNG] Non-"inline" abspos needs to ignore floats and text-indent.
This fixes two tests, but will also eventually benefit
floats-wrap-inside-inline-00[1234].htm in fast/block/float/, which are
currently passing because the absolutely positioned box in the test forces
its container to have block children. There's special-code for NG (which we
should remove) in LayoutBlockFlow::AddChild() that forces this (and causes
other problems).
Added a new test, to make it clear what this fix is about.
Bug: 734554
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: Ia2c0e0b2ab61999207114fdf935880fabc2e677c
Reviewed-on: https://chromium-review.googlesource.com/1116959
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571054}
--
wpt-commits: 12b9b4c9d40504a6d5df9339d7680a8a89184f18
wpt-pr: 11697
MozReview-Commit-ID: 9VzFxid8Ry8
Automatic update from web-platform-testsAsync Cookies: Implement sameSite attribute.
This CL modifies RestrictedCookieManager to allow renderers to set the
SameSite and Priority CanonicalCookie attributes. Renderers must be
allowed to set the SameSite and Priority attributes so that
RestrictedCookieManager can be used to implement the document.cookie
setter.
Bug: 856364, 729800
Cq-Include-Trybots: luci.chromium.try :linux_mojo
Change-Id: Ic0a520bc6c02c259ef22175c9eb161086fa18782
Reviewed-on: https://chromium-review.googlesource.com/1115586
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570976}
--
wpt-commits: 5392b81b526e3e0bbe805f1407a235d640f879a5
wpt-pr: 11696
MozReview-Commit-ID: 8dBERNSQC7I
Automatic update from web-platform-testsMove AudioBufferSourceNode tests to WPT
These tests basically pass on Firefox. If they don't, it's because
Firefox is incorrect and issues have been filed for these.
During the testing, we discovered that an incorrect assumption was made
that calling start() would always work. Because of test failures in Firefox,
this assumption is incorrect.
Updated audit.js to latest Chrome version (to get loadFileFromURL) and
add wpt lint exception for a console message in audit.js.
Needed to update audiocontext-getoutputtimestamp.html to make bots happy
because the AudioContext is running now on the bots, so time is
progressing, so the time stamps aren't always zero.
Bug: 745778
Change-Id: I5f9ee01498678db0feb57051f682772ca7bd9fbb
Reviewed-on: https://chromium-review.googlesource.com/1040865
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570890}
--
wpt-commits: 4d9bf95859072bac1680dff77c81cb640db6a6a5
wpt-pr: 10830
Automatic update from web-platform-tests[wptrunner] Correct profile installation for Fx 61 (#11693)
Extend the profile installation logic to account for a transitional
phase in the format of the Firefox profile directory. More detail is
available at:
https://bugzilla.mozilla.org/show_bug.cgi?id=1471419
--
wpt-commits: 4a983bf597c9120959bab2cc4f84b29c72501037
wpt-pr: 11693
Automatic update from web-platform-testsFix the clicked iframe in two wpt fullscreen tests.
With User Activation v2, activating a parent frame doesn't activate
its subframes. We fixed these two tests by sending the click to
subframes. This needed a workaround in auto-click.js because
the mutation observer there in doesn't seem to work when a button
element is added to a subframe.
Bug: 802371
Change-Id: I786668c87b802565e99ad16223cafc8ac1fd6296
Reviewed-on: https://chromium-review.googlesource.com/868323
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570778}
--
wpt-commits: b0f0ef9adb50765ea38be619015bb061d6a224b6
wpt-pr: 11678
Automatic update from web-platform-tests[WebAudio] throw an error when buffer has been already set.
should throw an InvalidStateError when buffer has been already
set in ConvolverNode
Bug: 709656
Change-Id: Ia0826f9ffa2e180da1311f4cded8ff7fe5461147
Reviewed-on: https://chromium-review.googlesource.com/1077713
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#570767}
--
wpt-commits: b44c26506446c1d95c644786254774255a96ffc1
wpt-pr: 11239
Automatic update from web-platform-testsAdd test for the removal of trailing spaces when preceding <br>
Blink and WebKit fails to remove trailing spaces preceding
`<br>`. This patch adds a test for that case. Gecko, Edge, and
the current build of LayoutNG passes this test.
This was originally reported at http://crbug.com/40634. It
turns out that fast/text/emphasis-overlap.html relies on this
behavior. Before removing the reliance, adding this test to
ensure this case is covered and to prevent regressions in
LayoutNG.
TBR=eae@chromium.org
Bug: 40634
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Change-Id: Iff877bac1c27c8689bdbc6949d01a9ea380463bd
Reviewed-on: https://chromium-review.googlesource.com/1116622
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570744}
--
wpt-commits: 2a423b054124f73b1d71eba4f782c7ff4a343898
wpt-pr: 11684
MozReview-Commit-ID: LqVXYAqe2Yq
Automatic update from web-platform-testsStart running wptserve/serve tests on Py3 (#11669)
While this may seem pointless when almost all of them are marked as
xfail on Py3, it does at least mean we have to keep them importable
and should mean we don't regress code that currently works on Py3.
--
wpt-commits: a8d56dbac2ef9be373868b2f2fd2302cc522ffab
wpt-pr: 11669
Automatic update from web-platform-testsLoosen assumptions so actual implementations match them (#11677)
--
wpt-commits: 865d9b467e226e3c69d7cc1eee7849dca0973eee
wpt-pr: 11677
Automatic update from web-platform-testsRefactor and split up quirks tests
The unitless-length test was a flaky timeout in chromium.
https://bugs.chromium.org/p/chromium/issues/detail?id=646133
--
wpt-commits: cea6203ed144fd0dd4abdfd28435ddfc5404c8e0
wpt-pr: 11641
Automatic update from web-platform-tests[encrypted-media] Add segmented clear-to-encrypted test. (#11308)
This adds a test that tests transitioning from clear to encrypted
content when it appears in different segments. This can happen when
streaming and the first content is a clear ad and the encrypted content
will be appended later.
This kind of content wasn't playable on Firefox until recently and I
think this wouldn't work on Edge if they supported clear-key.
https://bugzilla.mozilla.org/show_bug.cgi?id=1454630
--
wpt-commits: f240b8f22eea1a0fbff0fe48225973775b1524c3
wpt-pr: 11308
