mLastOverFrame is a WeakFrame, it could possibly be nulled-out, for example
after restyling, and the sub-document won't be able to be notified the mouse
leaving.
Differential Revision: https://phabricator.services.mozilla.com/D98787
When ibus input method is changed, Firefox reinitializes the KeymapWrapper
object, causing duplicate calls to g_signal_connect. If Firefox is running
long enough, duplicate handlers accumulate, and Firefox starts to barrage the
X server with XkbGetUpdatedMap/XkbGetControls calls, slowing the X server and
itself down.
A symptom of this problem is that after switching the input methods, Firefox
ignores the input for a while (up to several seconds).
Differential Revision: https://phabricator.services.mozilla.com/D98847
Automatic update from web-platform-tests
Support 'disclosure-open' and 'disclosure-closed' for 'list-style-type'
property
* core/css, core/style, web_tests/external/wpt:
Changes to recognize new keywords 'disclosure-open' and
'disclosure-closed'.
* layout/layout_details_marker.*,
layout/layout_tree_as_text.cc,
paint/details_marker_painter.*:
Changes to make DetailsMarkerPainter::GetCanonicalPath() static in
order to share it with ListMarkerPainter.
These files has no behavior changes.
* paint/list_marker_painter.cc:
Calls DetailsMarkerPainter::GetCanonicalPath() to get a Path, and draw
it on |context|.
* layout/list_marker.cc:
Adjust the layout size for 'disclosure-*'.
The size of 'circle', 'disc', 'square' is "ascent * 1 / 3", and it's
too small for 'disclosure-*'. We apply "font_height * 2 / 3" instead,
and it's same as the default size of ::-webkit-details-marker.
* layout/list_marker_text.cc, wtf/text/character_names.h:
Add text representations of 'disclosure-open' and 'disclosure-closed'.
This CL adds a simple rendering test. A following CL will add more
coverage.
I2S: https://t.co/1a7z357RV9
Bug: 590014
Change-Id: I1acad5a102c7cfcc91101fca283fde32fefae06f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567548
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833566}
--
wpt-commits: 92a7e0486f73461372fe6b93009f16f5ab6cfe29
wpt-pr: 26732
Automatic update from web-platform-tests
serial: Export manual tests into Web Platform Tests
These tests don't have any automation dependencies (since they are
manual) so can be exported first.
Bug: 884928
Change-Id: I6a3b9240d7ce8d61bfea43e5445d1334725bbd64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572745
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833542}
--
wpt-commits: 1cc8547873324c7b70ab00e5d2f7d6d0b0b59774
wpt-pr: 26752
Automatic update from web-platform-tests
Simulate user inputs in css/selectors/focus-visible-004.html
Use testdriver Action API to simulate mouse click actions in
css/selectors/focus-visible-004.html.
Bug: 1145677
Change-Id: I3715e32893f0e977226412d8ffc8b6928ff7a1a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551803
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833520}
--
wpt-commits: 733dbcfd53c36c69104b24b27b3cc44e09b6a3fa
wpt-pr: 26626
Automatic update from web-platform-tests
Simulate user inputs in pointerevent_capture_suppressing_mouse.html
Use testdriver Action API to simulate mouse actions in
pointerevents/pointerevent_capture_suppressing_mouse.html.
Bug: 1145677
Change-Id: I329d4b814020dd3c0d22c807c36828f5e868b4cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568825
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833510}
--
wpt-commits: 88780a69aa6ef42becab170fc1ddec9e5a61704e
wpt-pr: 26724
Automatic update from web-platform-tests
usb: Support composite devices using the WinUSB driver
This adds support for an uncommon configuration in which a composite USB
device has the WinUSB driver loaded for the whole device rather than
using Microsoft's composite driver to create device nodes for each
device function.
A manual test which confirms that all calls to claimInterface() succeed
or fail in a reasonable time has been added.
Bug: 1150758
Change-Id: If86d2e21dbc575cadea943a9c319029a10c78b36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568546
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833505}
--
wpt-commits: 7f680aee5f41278be2b4146b7669b5cc8caec47f
wpt-pr: 26713
Automatic update from web-platform-tests
Simulate user inputs in css/selectors/focus-visible-003.html
Use testdriver Action API to simulate mouse click actions in
css/selectors/focus-visible-003.html.
Bug: 1145677
Change-Id: I18d3862d524c0a917c056891e7012c589b8252e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548197
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833502}
--
wpt-commits: c7c5d9402225a17a0c13d58747d4d0088b299d46
wpt-pr: 26624
Automatic update from web-platform-tests
Test closing multiple datachannels
Tests that when a PeerConnection closes, all open datachannels
get the error and close events.
(The bug was fixed earlier, but this adds a test for it)
Bug: webrtc:6881
Change-Id: I4734f3d29333dcad98c34cf5dbdc8d4b04a5f986
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568278
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833346}
--
wpt-commits: dc60fe2cbd1292bb2166feba1f24971969e26154
wpt-pr: 26716
Automatic update from web-platform-tests
[CORS-RFC1918] Adding WPT tests for fetch in insecure contexts.
Adds tests verifying that fetch takes into account the CORS-RFC1918
restrictions regarding secure contexts.
These tests are ran with the CORS-RFC1918 flag as a virtual suite
because the flag currently breaks other non related tests due to
inheritance rules not being implemented.
Bug: 1138907
Change-Id: I0b5241c0ed13b4b6247310f19fdd0889351ee54b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517593
Commit-Queue: Arthur Hemery <ahemery@chromium.org>
Reviewed-by: Titouan Rigoudy <titouan@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833313}
--
wpt-commits: 9533c723edd37e31e092edcb6bbf29c636d2f087
wpt-pr: 26575
Automatic update from web-platform-tests
DOM: signal support for addEventListener()
Tests for https://github.com/whatwg/dom/pull/919.
--
wpt-commits: 625e1310ce19e9dde25b01f9eda0452c6ec274da
wpt-pr: 26472
Automatic update from web-platform-tests
Simulate user inputs in input-events/input-events-get-target-ranges.html
Use testdriver Action API to simulate key actions in
input-events/input-events-get-target-ranges.html Added . We have to
disable it because we do not support key actions in gpuBenchmarking
when running the tests in our chromium bots.
Bug: 1145677
Change-Id: I5176f374aaa79d771a78ef651f63098f039101da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533965
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833135}
--
wpt-commits: 4ac59dc8fb85817b4cf8fc801b524ed74743d2c1
wpt-pr: 26514
Automatic update from web-platform-tests
FontAccess: Fail concurrent font chooser requests
This changes the behavior from concurrent font chooser requests all
returning the same data from a single chooser invocation to failing a
subsequent request.
As implemented, the User Activation check will consume the activation,
failing any other in-flight requests.
Fixed: 1149621
Change-Id: If14e7e12ff52967e8dc49c383a66da94995c9134
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568931
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Auto-Submit: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833129}
--
wpt-commits: 6053b17de25520801d0534efbf3f7d200104ece0
wpt-pr: 26727
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request https://github.com/whatwg/html/pull/5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
Victor Porof
Edgar Chen
Tim Giles
Simon Giesecke
WGH
Kershaw Chang
Tom Ritter
Josue Quilon
Daisuke Akatsuka
Brindusan Cristian
Sylvestre Ledru
Mihai Alexandru Michis
Cristina Coroiu
moz-wptsync-bot
Kent Tamura
Reilly Grant
Lan Wei
autofoolip
Harald Alvestrand
James Graham
Hiroshige Hayashizaki
Arthur Hemery
Benjamin Gruenbaum
Olivier Yiptong
David Van Cleve