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
This patch changes 'TEST 3' so that instead of testing that all the
documents' document.fonts.ready Promises are resolved at a certain time, that
instead it just waits for them to resolve and then checks that they resolved
to the correct object.
The test previously assumed that calling SpecialPowers.pushPrefEnv on the
page's 'load' and waiting for pushPrefEnv's callback would be enough time
for document.fonts.ready to have been resolved for the top-level document and
all of its frames. That is not necessarily the case. Even the Promise in the
top-level document itself is not guaranteed to have resolved by that point.
The Promises will not have been resolved at least until style and layout has
been flushed, and in fact in Mozilla's implementation it frequently won't
happen until the first refresh driver tick after layout has finished. The
result of this is that the CI machine 'Linux x64 QuantumRender opt' was
failing 'TEST 3' intermittently.
Crash reports indicate that SourceBuffer::mStatus is not set, and thus
SourceBuffer::AppendFromInputStream crashes due to dereferencing an
invalid Maybe<nsresult> object. Since SourceBuffer::Append cannot fail
without mStatus being set (or already set), it must mean that the input
stream failed to read all the data, and swallowed any internal errors.
While we used to assert in this situation, we also silently swallowed
the error historically. This patch will check mStatus, but if it is
unavailable, it will assert like before, and silently return otherwise.
Luke Bjerring
Fredrik Söderquist
Nicolas Pena
Philip Jägenstedt
moz-wptsync-bot
Mike West
Philip Jägenstedt
Anne van Kesteren
Kent Tamura
Brandon Maslen
André Bargull
Justin Wood
Jonathan Watt
Eliza Balazs
Andrew Osmond