Until bug 1617002 Firefox would unintendedly not get unredirected on X11
when used with WR and OpenGL as it didn't fullfill the requirements -
not being transparent.
Now that this is fixed, fullscreen unredirection can happen on certain
compositors. For the basic compositor we already explicitely ask to not
get unredirected - do that for all backends.
Also adapt tests accordingly.
Differential Revision: https://phabricator.services.mozilla.com/D92180
Until bug 1617002 Firefox would unintendedly not get unredirected on X11
when used with WR and OpenGL as it didn't fullfill the requirements -
not being transparent.
Now that this is fixed, fullscreen unredirection can happen on certain
compositors. For the basic compositor we already explicitely ask to not
get unredirected - do that for all backends.
Also adapt tests accordingly.
Differential Revision: https://phabricator.services.mozilla.com/D92180
The patch no longer applies cleanly because of nearby changes in 4b8cb665a1.
Instead of forking a clang-12 version of this patch, we can get away with carrying a little less context in our patch file.
Differential Revision: https://phabricator.services.mozilla.com/D91625
The only caller passed in DisplayRelativeTo::ScrollFrame.
Removing this makes it easier to consolidate display port options
in a subsequent patch.
Differential Revision: https://phabricator.services.mozilla.com/D92014
Automatic update from web-platform-tests
Tweak some subsup tests to make them less strict (#25871)
These tests are sometimes failing on firefox locally, because they
depend on the font used. Also the rules when a MATH table is not
used are not clear yet and spec and implementations differ. This
commit tweaks subsup tests so that:
- They use Ahem rather than system fonts.
- Error is relaxed.
- position of sup/sup script is checked to be above/below the middle
of the base than close to the top/bottom of the base.
--
wpt-commits: a1d3637978a5de61b2b6008fa9fdbae1682c7e4d
wpt-pr: 25871
Automatic update from web-platform-tests
[mathml] Improve feature detection for operator dictionary test (#25619)
* [mathml] Improve feature detection for operator dictionnary test
The operator dictionary test compare various properties with an
explicit attribute set VS the default dictionary value. If the
feature corresponding to that property is not supported, then the
test will just return false positives. Feature detection was
implemented for spacing and movablelimits. This commit implements
the detection for the remaining properties (largeop, stretchy,
symmetric). This requires a special test font and so only
async feature detection functions are possible.
* move operator detection into a separate file
--
wpt-commits: 1918e328d632ab5b15096c26bd1400dcba7dd4e5
wpt-pr: 25619
Automatic update from web-platform-tests
[COOP] access reporting: Fix WPT flakes.
The WPT testharness.js is defining:
```
WindowTestEnvironment.prototype._forEach_windows = function(callback) {
// Iterate over the windows [self ... top, opener]. The callback is
// passed two objects, the first one is the window object itself, the
// second one is a boolean indicating whether or not it's on the same
// origin as the (...)
```
This causes some postMessage to be sent cross-window. They are detected
by the Cross-Origin-Opener-Policy-Report-Only.
In general, we must ensure that testharness.js isn't used together with
access checks. This patch removes the ones for all the tests depending
on test-access-property.js
Bug: 1090273
Change-Id: I9f13406783d4f5a1d28205b6492ab1b3318c50b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436743
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Commit-Queue: Pâris Meuleman <pmeuleman@chromium.org>
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811734}
--
wpt-commits: 32fede7cfb4d86ff5dc7465318726b6d26487503
wpt-pr: 25842
Automatic update from web-platform-tests
content-visibility: Ensure to keep the DL unlocked if targeted by scroll
This patch generalizes the find-in-page fix we had previously to also
apply to other methods that can use to scroll the viewport to the
element in a locked subtree. Specifically, this keep the lock unlocked
for two frames to ensure that the visibility notification kicks in to
keep it unlocked until the user scrolls away.
R=chrishtr@chromium.org
Bug: 1132869
Change-Id: I598f82f73429e41839a6675321eb6fb1eb84f6b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435808
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811709}
--
wpt-commits: 40054823417b7d08bae15dd6a7f80c582debdfde
wpt-pr: 25821
Automatic update from web-platform-tests
Change writing-mode in vertical underline thickness test
Replace sideways-lr writing mode with more widely supported vertical-lr
in text-decoration-thickness-vertical-002.html and update
text-underline-position: from-font. This makes this underline test
compatible with Chromium while preserving the logic of the test.
--
wpt-commits: 415970897863eeac92e090384620fede90f77173
wpt-pr: 25789
Automatic update from web-platform-tests
[COOP] access reporting: split property.https.html test. (#25824)
Since:
https://chromium-review.googlesource.com/c/chromium/src/+/2428976
the "receive" timeout is now infinite. It means all the tests in
property.https.html will either all succeed or if one of them fails, it
will timeout.
This patch split the test in order to get individual results. This
allow us to prevent individual regression.
Bug: 1090273
Change-Id: I5629e4130dbabde44755468bc7b28ea0d0e802f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435638
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811249}
Co-authored-by: arthursonzogni <arthursonzogni@chromium.org>
--
wpt-commits: 2194841795c619ddb562bd6f10a79e8b207bdeae
wpt-pr: 25824
Automatic update from web-platform-tests
[Trusted Types] Fix eval handling in workers.
The current code only enables/disables eval (& Function constructors) in
workers wholesale, and never registers a callback. This means that the
functionality that relies on the callback doesn't work in workers.
This patch registers the callback, and removes two assertions that are now
no longer true.
Bug: 1126472
Change-Id: I3996431acd97fd6f62e8e09ed44732e8eaa438f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426645
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811633}
--
wpt-commits: aaa6409d570a376d982475c94fd1c0baf831d843
wpt-pr: 25820
Automatic update from web-platform-tests
[wpt] Fix tests/test_wpt.py::test_tests_affected_idlharness (#25835)
This test uses a real commit and real set of idlharness tests to
test the 'affected by' logic. When a new webrtc idlharness test
dependency was added, the list of dependent files changed and the test
started failing. Quick fix to unblock it is to just add the new test.
See https://github.com/web-platform-tests/wpt/pull/25774#issuecomment-700600138
--
wpt-commits: e4c3ee00cfa1f8a093f71d75d8f9efb941bef9b3
wpt-pr: 25835
Automatic update from web-platform-tests
[Text Decorations] Compute ink_overflow
Text Decorations were not contributing to ink_overflow,
leading to remnants on the screen when invalidated and
causing the mis-sizing of composited layers containing
the decorations.
This change adds ink overflow calculations for LayoutNG
fragment items. Legacy layout is unaffected.
Tests added include both the paint layer sizing concern
and the invalidation concern.
Bug: 896295
Change-Id: I3b8cfd9d9c4f3efafd380e6718fd2eaf22229f27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422356
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811524}
--
wpt-commits: 7ca7f33a83cf7c0f90d6bbf58dc8a1aeb700397d
wpt-pr: 25665
Automatic update from web-platform-tests
[PTZ] Add missing tests for pan and tilt in applyConstraints()
This CL adds similar tests to zoom for pan and tilt constraints when
calling applyConstraints with invalid values.
Bug: 934063
Change-Id: I0d7926ba5c887604fc77c0854e3d3fccea784f5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435640
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#811615}
--
wpt-commits: 8804dfa8b84dcf0f92d6147555113e1be38b216b
wpt-pr: 25816
Automatic update from web-platform-tests
Test case for the css handling of U+000D (#25830)
Relates to https://github.com/w3c/csswg-drafts/issues/5410
--
wpt-commits: 6730dabbcc826e8ccbd6a9ee43d67c65e8626f29
wpt-pr: 25830
Automatic update from web-platform-tests
[css-flex] Fix flex base size for aspect ratio items of column flexboxes
This is very similar to
https://chromium-review.googlesource.com/c/chromium/src/+/2399082 ,
which dealt with items whose inline axis was the flexbox's main axis.
This patch deals with items whose block axis is the flexbox's main axis.
Old behavior: Use post-layout height of image items, obeying
min/main/max height.
New behavior: use the intrinsic height after applying the aspect ratio
and min/main/max width. Ignore computed min/main/max height.
Fixed: 987000
Change-Id: If64eeca9cc541bec863b1132aea4fd89305f5d9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2433629
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811420}
--
wpt-commits: f7aef3ea8fb082ae46f99a4fa161336e7ea2eb2d
wpt-pr: 25807
Automatic update from web-platform-tests
[COOP] access reporting: Use infinite timeout for receive.
Some browsers do not implement COOP reporting. As a result, no reports
are received after a 2.5s timeout.
Waiting 2.5s many time can reach the global timeout. Sometime, this
flakes in between FAIL and TIMEOUT.
This patch makes the timeout to be infinite by default to get consistent
failure.
Bug: 1090273
Change-Id: I081b9c8e944fc50b391753ce0948392b88d3fd0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2428976
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810604}
--
wpt-commits: dbb8a3ff33b3cca0899018e7dee3989842017976
wpt-pr: 25787
Automatic update from web-platform-tests
Only reset trailing_collapsible_space_ structure if it has value
The crash described in the issue 1132762 was caused by our rencet change
in r811115, to ensure the trailing_collapsible_space_ structure is reset
when the associated item_result changed.
However, there was an error in the condition, so that we should ensure
we only call the 'reset()' function when the Optional has value.
Bug: 1132762, 1132811
Change-Id: I73d10c309162649e143cd66ff7702c4ac7e5eed2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435388
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811288}
--
wpt-commits: c9da4e292335ec2614049da3fa1eb43f05754d3b
wpt-pr: 25819
Robert Mader
Paul Bone
Mark Hammond
Razvan Maries
Jan-Ivar Bruaroey
Daisuke Akatsuka
Olli Pettay
David Major
Peter Van der Beken
Timothy Nikkel
Cameron McCormack
Cosmin Sabou
Botond Ballo
Itiel
moz-wptsync-bot
Alwin Blok
Frédéric Wang
Gérard Talbot
Domenic Denicola
arthursonzogni
Vladimir Levin
Dominik Röttsches
Blink WPT Bot
Daniel Vogelheim
Stephen McGruer
Stephen Chenney
Francois Beaufort
Florian Rivoal
David Grogan
autofoolip
Javier Fernández García-Boente