Automatic update from web-platform-tests
[@container] Invalidate container-relative units in @container prelude
The internal CSSContainerValues of a ContainerQueryEvaluator
as of recently contains a CSSToLengthConversionData::ContainerSizes
object which caches the values used for resolving container-relative
units. This cache needs to be invalidated, otherwise affected queries
will not be responsive to changes.
This is roughly the same problem as the 'rem' unit invalidation that
was fixed recently, so we can generalize that to solve the current
problem.
Note that this CL removes font_dirty_=true that previously took
place in RootFontChanged. This flag doesn't fit anymore with the
generalization (UpdateValuesIfNeeded), but it's also actually not
needed for the 'rem' unit case, since we anyway recalculate the style
of all descendants.
Fixed: 1340232
Change-Id: I7acfb475d1b7d08c84fdf09b7fb0be6b608d0c26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3731812
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1018817}
--
wpt-commits: 2f9a2a84ac665f1a8ab1fe722902b5fe61bfdf47
wpt-pr: 34625
Automatic update from web-platform-tests
Need post-layout fragments on fragment item cache hit.
We previously used to always get post-layout fragments when cloning a
fragment item, but CL:3677013 changed that, since it's no longer a given
that we always do want the post-layout fragments, and that the callers
rather fetch the post-layout fragments at their own discretion.
Back when I wrote that CL, I didn't realize that
NGFragmentItemsBuilder::AddPreviousItems() relied on getting post-layout
fragments as well (probably because cs.chromium.org failed to list all
call sites to NGFragmentItemsBuilder::ItemWithOffset::ItemWithOffset()).
Bug: 1340168
Change-Id: I5f799aa5305c7588d7a6034b2f8eab33b8e1a89c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3731811
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1018694}
--
wpt-commits: dfb10692e649e537946ef5db98898649c9010d98
wpt-pr: 34624
Automatic update from web-platform-tests
Allow hide animations to be started from pop up hide event
See [1] for the origin of this change, which makes it possible to
trigger pop up hide animations from within the `hide` event handler.
For example:
popup.addEventListener('hide', () => {
popup.animate({
transform: 'translateY(-50px)',
opacity: 0,
}, 200);
});
To accomplish that, the hide process now looks like this:
1. Capture any already-running animations via getAnimations(),
including animations on descendent elements.
2. Remove the :top-layer pseudo class.
3. Fire the 'hide' event.
4. If the hidePopup() call is *not* the result of the pop-up being
"forced out" of the top layer, e.g. by a modal dialog or fullscreen
element:
a. Restore focus to the previously-focused element.
b. Update style. (Animations/transitions start here.)
c. Call getAnimations() again, remove any from step #1, and then wait
until all of them finish or are cancelled.
5. Remove the pop-up from the top layer, and add the UA display:none
style.
6. Update style.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/3688871/9/third_party/blink/renderer/core/dom/element.cc#2660
Bug: 1307772
Change-Id: I910535b13cfc3c8f8498ed64dae73caa75dd7317
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3708419
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Commit-Queue: Robert Flack <flackr@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1018685}
--
wpt-commits: d4a7c77961af00b9a4ba78b0f80d771a519f78c6
wpt-pr: 34561
Automatic update from web-platform-tests
[@container] Test invalidation of font-relative units separately
This WPT changed both the root font and non-root font at the same,
which means one invalidation mechanism may overlap. Test each unit
separately instead.
Bug: 1339808
Change-Id: I18fcef9f92358c437bb5c547132f8a5348c0d39f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3726452
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1018645}
--
wpt-commits: a19cb86d9e1fce816ddd8f2055d9c60ac6119fdc
wpt-pr: 34603
Automatic update from web-platform-tests
Fetch: add Set-Cookie as an invalid request header
See https://github.com/whatwg/fetch/pull/1453 for context.
--
wpt-commits: 5fb9aee1a0d59531dbe4be9300d4036e00ba2eb5
wpt-pr: 34424
Automatic update from web-platform-tests
Rename CanvasFilter WPTs to be tentative
The spec is being reverted per https://github.com/whatwg/html/pull/7874 due to lack of multi-implementer interest. So, we need to rename the tests.
Bug: 1169216
Change-Id: I059fa4c951f2076cffb562bf4a32d4e4284d3771
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3714402
Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1018614}
--
wpt-commits: 0c579dc895666e989c046b706955ca19d1244c7d
wpt-pr: 34536
Automatic update from web-platform-tests
Resolve FIXME in LayoutQuote by using English quotes as default
Legacy FIXME in layout_quote.cc to change default "quote" (%22) to
English “quote” (%E2%80%9C, %E2%80%9D). Fixed all affected tests.
Change-Id: I0dcff0d2356ccbf53ebb16e3ad8abe930f410a50
Bug: 753671
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3704099
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1018608}
--
wpt-commits: 0b8d6e703759e62ee7439687d88144a46b881d66
wpt-pr: 34519
Automatic update from web-platform-tests
`await_promise` is mandatory (#34577)
Make `script.evaluate`->`awaitPromise` mandatory.
Co-authored-by: Maksim Sadym <sadym@google.com>
--
wpt-commits: a59332b7317247a99cfa75d9fa79e0816f5fbcfe
wpt-pr: 34577
With TI we had a cache for this but we got rid of it when we removed TI. This patch
adds back a simpler version of it that caches the four most recently created
shapes. This cache has a good hit rate on the web and on Kraken's json-parse-financial
test.
Differential Revision: https://phabricator.services.mozilla.com/D150558
I checked that skipping the test does not move the intermittent to the next test.
I am not sure what makes this test problematic, I suppose this has to do with initializing widgets in the inspector to handler filters.
Let's skip this on linux for now.
Differential Revision: https://phabricator.services.mozilla.com/D150859
de -> 7e0a17ca783667e7514b5e13097f14a414a581dd
ko -> 422482b1d9efcd9132f7d1c155378f0fad13a25a
pt-BR -> 564c5d512059fd8bc597f66193241084f6b112c9
tg -> fe59cfc0c58d352d10fd3f82fe90c54a49122350
uk -> d77a7d270d57167a98f03116455dc50c3f896ffc
The virtual click event is also removed. It seems this event is only used to check whether this was a key or mouse event in PanelMultiView.jsm
This also removes support for pressing the enter key to trigger these toolbarbuttons on Mac which shouldn't be happening anyway.
Differential Revision: https://phabricator.services.mozilla.com/D149285
Anders Hartvoll Ruud
Morten Stenshorne
moz-wptsync-bot
Mason Freed
Luca Casonato
Rune Lillesveen
Noam Rosenthal
Domenic Denicola
Di Zhang
Maksim Sadym
dependabot[bot]
kernp25
Josue
Jan de Mooij
Daniel Q
Raphael Ferrand
serge-sans-paille
Mozilla Releng Treescript
Julian Descottes
Alexandra Borovova
Norisz Fay
Neil Deakin
Iulian Moraru
Updatebot
Timothy Nikkel
sotaro
criss