* Create BLOCKQUOTE internal role (also needed for correct exposure of
blockquote element on ATK)
* Add new ARIA roles to internal ARIA map
* Add new roles to existing ARIA roles mochitest and update blockquote
element test to reflect mapping to the new internal role
Automatic update from web-platform-testsImplement policy: 'document-stream-insertion'
This CL adds the actual implementation for the experimental policy
'document-stream-insertion'. The policy is used to block usages of
specific APIs mentioned section "dynamic markup insertion" of the HTML
spec. This essentially includes document.{close, open, write, writeln}.
With the current CL, the calls to banned API lead to a DOMException.
The feature itself was introduced in a previous CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1053349
Bug: 841605
Change-Id: I1a764bc7545a0d26a29d217027cf43e561d8dfbd
Reviewed-on: https://chromium-review.googlesource.com/1058138
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561275}
--
wpt-commits: 314de955a5102650136404f6439f22f8d838e0f4
wpt-pr: 11022
Automatic update from web-platform-testsSplit the layout test for remove-track
Keep separate tests for in-band and out-of-band text tracks.
Bug: 826419
Change-Id: I2e888d47ddda080bbc7b6cd6f1f645d064c5a6fa
Reviewed-on: https://chromium-review.googlesource.com/1070570
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561269}
--
wpt-commits: cdec7db504d74c9a6f371a05d92f2be35ac8cc60
wpt-pr: 11135
Automatic update from web-platform-testsAllow Text node in elementsFromPoint if descendant of SVG text content
When hit-testing, SVG text content nodes will use their Text node
descendants as the inner-most/hit node, and hit-testing will not be
performed in any of the background phases. Thus we need to selectively
allow Text node which has an SVG text content element as their parent.
Bug: 842504
Change-Id: Ie282d5e9a66880f3f0d5e319b249f5f41db9e9db
Reviewed-on: https://chromium-review.googlesource.com/1059753
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561238}
--
wpt-commits: 65a5c24ba9769da8b103f72349ea111b124e54db
wpt-pr: 11130
Automatic update from web-platform-testsAdd a simple test for ResourceTiming |name| with Service Workers
This CL adds a test to check that the |name| of Resource Timing entries
is the original request URL even when a service worker uses
respondWith(fetch()) to respond with a different response URL.
Change-Id: I4fe61395c6d7c3b1b5fb5e4f131b131d90c33154
Reviewed-on: https://chromium-review.googlesource.com/1065013
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561228}
--
wpt-commits: 9633890103f1a7025405cab78b00bb318ed9ebc4
wpt-pr: 11058
Automatic update from web-platform-testsRename foreign-object-paints-before-rect-expected.html to -ref.html
The naming of refs is not enforced in wpt and this was not broken, but
see https://bugs.chromium.org/p/chromium/issues/detail?id=844781#c9
for things that can go wrong. We might add a lint/presubmit check.
Bug: 842668
Change-Id: Ia2952a3720df88e323c8af17f87d05c6f07cfad7
Reviewed-on: https://chromium-review.googlesource.com/1069131
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561138}
--
wpt-commits: 4698cffbd33ce8e20b8ae6c6c3032569999d78b2
wpt-pr: 11118
--HG--
rename : testing/web-platform/tests/svg/extensibility/foreignObject/foreign-object-paints-before-rect-expected.html => testing/web-platform/tests/svg/extensibility/foreignObject/foreign-object-paints-before-rect-ref.html
Automatic update from web-platform-testsNavigation fragment decode and encodings (#8723)
* Navigation fragment decode and encodings
See https://github.com/whatwg/html/pull/3111 for context.
* make tests more usable
* address review feedback
--
wpt-commits: 5b878a1e5de29aa4e68c48e0122878f983f036ff
wpt-pr: 8723
Automatic update from web-platform-testsURL/Encoding: change query state parsing
See https://github.com/whatwg/encoding/issues/139 for rationale and https://github.com/whatwg/url/pull/386 for the change to the URL Standard.
(I found all these resources in part due to @rakuco's work on trying to align Chrome with the earlier iteration of the specification.)
--
wpt-commits: e399a2c694345240639c23cc5e9e4f077a47cf30
wpt-pr: 10915
Automatic update from web-platform-testsFormData: Strings from form controls should be converted to USVStrings
This CL fixes a regression by crrev.com/560505.
Before r560505 such strings were converted to USVStrings implicitly
because FromData::Entry stored encoded CStrings, and text encoders
replace unpaired surrogates with U+FFFD. Since r560505 we don't apply
text encoding in FormData::Entry, and need to convert strings to
USVStrings explicitly.
This CL also adds DCHECKs to FormData::Entry constructors.
Bug: 845744
Change-Id: I9893848f4e32fbe3c0c7a8f787584fbbb8ba8e87
Reviewed-on: https://chromium-review.googlesource.com/1067560
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#560929}
--
wpt-commits: 6df97f3630e83ec0caf1854b559c488368436a68
wpt-pr: 11113
