Automatic update from web-platform-tests
[css-flex] Include gaps in intrinsic sizes for column-wrap flexboxes
The intrinsic sizing code borrows PlaceFlexItems from Layout, but
PlaceFlexItems doesn't handle gaps, AlignFlexLines does. We don't want
to bring all of AlignFlexLines into intrinsic sizing, so just add gaps
manually.
Fixed: 335328452
Change-Id: Ic97b04ab22766a894299a3b74d0feea3734041fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5486047
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1292562}
--
wpt-commits: 08418af6de2abeebc92b68bb423997ed3ba81029
wpt-pr: 45896
Automatic update from web-platform-tests
Move a prefers-color-scheme test to css/mediaqueries/ (#45887)
* Move a prefers-color-scheme test to css/mediaqueries/
Use the prefers-color-scheme.svg already in the target directory, and
adapt the test to use the blue/purple colors from that.
* Update prefers-color-scheme-svg-as-image-ref.html
--
wpt-commits: 4f1737843b28b72a0004133e6991a9741bca9b69
wpt-pr: 45887
Add one extra branch if we have before-change style but its display
is none, and the new style is not display:none. Also, we add an extra
subtest if we use the container query to change the display property.
Differential Revision: https://phabricator.services.mozilla.com/D208572
Now we use the starting style if we have, to replace the before-change
style. This includes a minor refactoring of the handling of transitions
because it becomes a little bit complicated.
Differential Revision: https://phabricator.services.mozilla.com/D208571
Per spec, we define starting style for an element as the after-change style
with @starting-style rules applied in addition.
If an element does not have a before-change style for a given style change
event, the starting style is used instead of the before-change style to
compare with the after-change style to start transitions.
The basic idea in this patch is:
1. We add a flag to indicate if this element may have starting style. We
set this flag during its full matching, and store this flag in the
element data.
2. So during process animations, we check this flag, if this element may
have starting style and specifies transitions, we resolve the
starting style. Use it as the before-change style.
The implmentation in process_animations() and tests are in the following
patches.
Differential Revision: https://phabricator.services.mozilla.com/D208570
The rules inside @starting-style doesn't apply to primary style, and
they are used only for CSS transitions (when computing starting style).
So adding a flag to make us easier to filter them out.
Differential Revision: https://phabricator.services.mozilla.com/D208569
This revision reverts the changes that trimmed non-breaking spaces from the
start and end of accessible names. The web platform group has decided that
those tests weren't valid as-is; the correct behavior is not to trim those
characters. This revision also removes expected-fail designations from
affected tests.
Differential Revision: https://phabricator.services.mozilla.com/D208687
One alternative approach would be to use AutoEnterOOMUnsafeRegion and crash if we OOM while recompiling an on-stack baseline script. I'm tempted, but this patch is simple enough that we can let this code live for now.
Differential Revision: https://phabricator.services.mozilla.com/D208559
During display list and scene building, there are two coordinate
remapping steps that occur:
1) From stacking context coords -> reference frame relative coords
2) From pre-scrolled coords -> removed external scrolling offsets
These were previously handled in one place, however we want to
split these up so that we can apply snapping _after_ step 1 but
prior to step 2. This will allow us to have fractional external
scroll offsets that don't affect snapping. These will be snapped
later on during frame build after applying any (possibly fractional
APZ scroll offsets). This is a cheap operation during frame building
as we only need to snap and modify the transform matrices, not
individual primitives.
This patch should have no functional changes, it's prep work for
the changes referenced above. It does move all of step 1 to be
done during DL building in the content process, and all of step
2 to be done during scene building in the GPU process. In future,
if/when we resolve the issues we have with reliance on cross-iframe
knowledge for fractional snapping, we can move step 2 (including
snapping) in to the content process as well.
Further, as part of the DL bypass work, we will need to remap coord
spaces during DL building in a differeny way, which this simplifies.
Differential Revision: https://phabricator.services.mozilla.com/D208427
The original code is necessary to make content documents in the parent process
on Android.
On Android each tab has an nsWindow instance regardless whether the top level
content document gets loaded in the parent process or in a content process, it's
a 1:1 relationship. Thus using the nearest widget of the root frame to obtain an
nsIWidget would be fine, it would be an nsWindow instance if the document is in
the parrent process, it would be an PuppetWidget instance if the document is in
a content process.
Differential Revision: https://phabricator.services.mozilla.com/D207670
It can avoid mixed-up nsBaseWidget::UpdateZoomConstraints calls for two initial
about:blank documents in the parent process.
Differential Revision: https://phabricator.services.mozilla.com/D207669
This patch is doing roughly three things:
- Adds a boolean field through the IR pipeline representing whether we want to
allow getters or not. This will allow us to do a VM call and all that jazz
within the op in order to actually call the getter
- Updates existing megamorphic handling to write information to the megamorphic
cache indicating that the property is a getter. Existing megamorphic handlers
will treat this as a cache miss and fail / bail
- Allows the tolerant VM calls to look up the cached getter in the megamorphic
cache and call it without having to do the full expensive property lookup
Differential Revision: https://phabricator.services.mozilla.com/D206148
The values that we take from our parent should be zoomed in. Similarly,
root values should also be zoomed in by the effective zoom (for that, we
unzoom root values to zoom-independent pixels when storing them on the
device).
Container-relative units probably need more care / thought, because they
are in the layout (so zoom-independent) coordinate space already, since
they come from frames. Bug 1894104 is filed for this.
Differential Revision: https://phabricator.services.mozilla.com/D208599
The skip-unless-mozlint optimization strategy replaces the use of 'when: files-changed'
with the mozlint config files.
Since the job config is different, also need to remove 'optimization' for code-review
flagged jobs on mozilla-central.
Differential Revision: https://phabricator.services.mozilla.com/D208636
