Automatic update from web-platform-tests
Remvoe the test cases that are not specified by the spec. (#33945)
These test cases were introduced while adding test cases for
step 7-9 https://html.spec.whatwg.org/multipage/input.html#input-type-change
with commit at
ed63c8c97b
It is correct with test cases for step 7-9. However, for cases that don't meet the requirement
for step 7-9, it assume that the selectionStart/selectionEnd stay as they are. This might be
always true. For example, selectionStart/selectionEnd could change when previouslySelectable and
nowSelectable are both true, yet the value changes due to sanitization.
--
wpt-commits: 4396e42eed59ae569a461551d40a95093eac28c4
wpt-pr: 33945
Automatic update from web-platform-tests
Reland "CSS highlight painting: bump HighlightOverlayPainting to stable"
This is a reland of commit abc6f616c7bc2c53cc9d8c44b82384d43dd77d02
Original change's description:
> CSS highlight painting: bump HighlightOverlayPainting to stable
>
> This patch enables the new highlight overlay painter. The rebaselined
> tests and their reasons are as follows:
>
> • no more double painting bug
> • dark-mode/colors/selection.html
> • originating decorations are now recolored per spec
> • editing/selection/line-wrap-2.html
> • virtual/text-antialias/selection/khmer-selection.html
> • spelling markers are now *consistently* painted over text
> • paint/markers/document-markers-font-8px.html
> • paint/markers/document-markers-zoom-2000.html
> • decorations are now clipped to highlight background rect
> • svg/text/text-selection-deco-01-b.svg
> • svg/text/text-selection-text-03-b.svg
>
> The only new failure expectations are as follows:
>
> • external/wpt/css/css-pseudo/highlight-painting-003.html broadens
> from Mac11 to Mac (like we had to do in CL:3608432)
> • external/wpt/css/css-text-decor/text-decoration-color-selection-001
> fails because the test is incorrect (bug 1321106)
> • paint/markers/suggestion-marker-basic.html fails because it’s not
> clear the assertion still complies with the spec (bug 1321114)
>
> Some tests had bugs that we’ve fixed in this patch:
>
> • external/wpt/css/css-pseudo/target-text-text-decoration-001.html
> had a bug where it assumed UA default highlight colors would be
> suppressed by an author ‘text-decoration’
>
> Bug: 1147859
> Change-Id: Ie4d8dae515a786fa01e8f2852d645f3a8ad313be
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3616170
> Reviewed-by: Stephen Chenney <schenney@chromium.org>
> Commit-Queue: Delan Azabani <dazabani@igalia.com>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1001604}
Bug: 1147859
Change-Id: Icd150ff8c695d20a5c9f44df45d5e0751c31f79a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3640642
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Delan Azabani <dazabani@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1001937}
--
wpt-commits: 2fdb8d7d1408e52601e8ccc5cdfd063740638116
wpt-pr: 34024
Automatic update from web-platform-tests
Remove inline scripts in isolated app tests
This CL removes inline scripts from all isolated app and direct socket
tests, moving their JS into separate files instead. It also adds trusted
types to tests that load scripts via URL. This is needed to comply with
the CSP that will be injected by crrev.com/c/3587460.
Bug: 1282071
Change-Id: I089d8f60f1852db23efe3d68c10a38db37e1598a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3636318
Reviewed-by: Andrew Rayskiy <greengrape@google.com>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Phillis Tang <phillis@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001836}
--
wpt-commits: c54c7d0f0d6000d720cfaf5bcd610d20333ac768
wpt-pr: 34001
Automatic update from web-platform-tests
Revert "CSS highlight painting: bump HighlightOverlayPainting to stable"
This reverts commit abc6f616c7bc2c53cc9d8c44b82384d43dd77d02.
Reason for revert: crbug.com/1324359
Original change's description:
> CSS highlight painting: bump HighlightOverlayPainting to stable
>
> This patch enables the new highlight overlay painter. The rebaselined
> tests and their reasons are as follows:
>
> • no more double painting bug
> • dark-mode/colors/selection.html
> • originating decorations are now recolored per spec
> • editing/selection/line-wrap-2.html
> • virtual/text-antialias/selection/khmer-selection.html
> • spelling markers are now *consistently* painted over text
> • paint/markers/document-markers-font-8px.html
> • paint/markers/document-markers-zoom-2000.html
> • decorations are now clipped to highlight background rect
> • svg/text/text-selection-deco-01-b.svg
> • svg/text/text-selection-text-03-b.svg
>
> The only new failure expectations are as follows:
>
> • external/wpt/css/css-pseudo/highlight-painting-003.html broadens
> from Mac11 to Mac (like we had to do in CL:3608432)
> • external/wpt/css/css-text-decor/text-decoration-color-selection-001
> fails because the test is incorrect (bug 1321106)
> • paint/markers/suggestion-marker-basic.html fails because it’s not
> clear the assertion still complies with the spec (bug 1321114)
>
> Some tests had bugs that we’ve fixed in this patch:
>
> • external/wpt/css/css-pseudo/target-text-text-decoration-001.html
> had a bug where it assumed UA default highlight colors would be
> suppressed by an author ‘text-decoration’
>
> Bug: 1147859
> Change-Id: Ie4d8dae515a786fa01e8f2852d645f3a8ad313be
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3616170
> Reviewed-by: Stephen Chenney <schenney@chromium.org>
> Commit-Queue: Delan Azabani <dazabani@igalia.com>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1001604}
Bug: 1147859
Change-Id: If712ce733dd1b232a033902bbda027dc3f9f8f05
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3639059
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Mike Wasserman <msw@google.com>
Commit-Queue: Mike Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001753}
--
wpt-commits: 2658ef8be3ebd3724f0361769a26f36e114376f5
wpt-pr: 34023
Automatic update from web-platform-tests
Fix MediaDevices-produceCropId WPT test
This patch fixes the currently broken produceCropId test. Due to an
issue with the test harness parsing an iframe, this test set is not
picked up and ran. The produceCropId API has also been finalized and
removed from the Element API, so some additional changes to fix the
actual tests as well.
Bug: 1314679
Change-Id: Ic967c6b2c2651ac9391078897219ed337a033513
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3596403
Reviewed-by: Elad Alon <eladalon@chromium.org>
Commit-Queue: Jordan Bayles <jophba@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001701}
--
wpt-commits: 7c24f153082a28d8883168e1fbb27708afbe608b
wpt-pr: 33715
Automatic update from web-platform-tests
Try again to fix the backdrop-animate-002 test on WPT.fyi
This test fails with off-by-one values on the green background. This
is attempt #2 to fix that, by adding fuzziness.
Bug: 1323293
Change-Id: I9f51f257ef0064b6cd144a32ae01b148ed881112
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3638193
Reviewed-by: Philip Rogers <pdr@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001695}
--
wpt-commits: 3238a6af508efb8e621676df5e2f803e760fb263
wpt-pr: 34020
Automatic update from web-platform-tests
[Azure Pipelines] Run Edge Canary only once a week (#34015)
--
wpt-commits: a5ef2947f2cc61e3785f9ebaf771b960e3ad17ef
wpt-pr: 34015
Automatic update from web-platform-tests
Only reflect valid popup values
This was resolved in [1] - only valid values for the `popup` attribute
should be reflected, so that feature detection can be used on the values.
[1] https://github.com/openui/open-ui/issues/491#issuecomment-1118927375
Bug: 1307772
Change-Id: I932a28bd48e336cf01253a971804dc00dcd099fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3639122
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001641}
--
wpt-commits: 1edef0f70fd0b8480c1c7af45307ecfaf3611414
wpt-pr: 34021
Automatic update from web-platform-tests
CSS highlight painting: bump HighlightOverlayPainting to stable
This patch enables the new highlight overlay painter. The rebaselined
tests and their reasons are as follows:
• no more double painting bug
• dark-mode/colors/selection.html
• originating decorations are now recolored per spec
• editing/selection/line-wrap-2.html
• virtual/text-antialias/selection/khmer-selection.html
• spelling markers are now *consistently* painted over text
• paint/markers/document-markers-font-8px.html
• paint/markers/document-markers-zoom-2000.html
• decorations are now clipped to highlight background rect
• svg/text/text-selection-deco-01-b.svg
• svg/text/text-selection-text-03-b.svg
The only new failure expectations are as follows:
• external/wpt/css/css-pseudo/highlight-painting-003.html broadens
from Mac11 to Mac (like we had to do in CL:3608432)
• external/wpt/css/css-text-decor/text-decoration-color-selection-001
fails because the test is incorrect (bug 1321106)
• paint/markers/suggestion-marker-basic.html fails because it’s not
clear the assertion still complies with the spec (bug 1321114)
Some tests had bugs that we’ve fixed in this patch:
• external/wpt/css/css-pseudo/target-text-text-decoration-001.html
had a bug where it assumed UA default highlight colors would be
suppressed by an author ‘text-decoration’
Bug: 1147859
Change-Id: Ie4d8dae515a786fa01e8f2852d645f3a8ad313be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3616170
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Delan Azabani <dazabani@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001604}
--
wpt-commits: 56ba00c14475459986c99f240e0b24e7e7ff5dc0
wpt-pr: 33889
Automatic update from web-platform-tests
WebKit export of https://bugs.webkit.org/show_bug.cgi?id=239831 (#34022)
Add test for hit-testing on pseudo-elements of inert nodes
--
wpt-commits: 764ba538c7fb6af0243f4cb1c069069a888615f0
wpt-pr: 34022
Automatic update from web-platform-tests
Fix block & unblock ordering when an inline style sheet mutates
When an inline <style> mutates, it calls AddPendingBlockingSheet() for
the new style sheet first, and then calls RemovePendingBlockingSheet()
for the old style sheet.
This used to be fine when those two methods were just adding /
subtracting some counters. However, after crrev.com/c/3503857, the two
methods become adding / removing the <style> element into / from the
RenderBlockingResourceManager class's set of pending elements, which
assumes that we never double-add or double-remove any element. Then the
relevant states are broken.
This patch reorders the call sites of the two methods to make sure we
remove it before re-adding it.
Fixed: 1323319
Change-Id: If28e35fb794e7bd2d77107ab4f8e867ad66d88ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3636301
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001530}
--
wpt-commits: 6533b73265da85295177a4c4b4ecf02d94b6100d
wpt-pr: 34005
Automatic update from web-platform-tests
Reland "Do not eagerly mark ancestors for repaint" with stacking bugfix
This patch relands https://crrev.com/984798 which was reverted due to
https://crbug.com/1323016. PaintLayer has a bit for self needing repaint
as well as a bit for descendant needing repaint. When marking a
PaintLayer for repaint, the ancestor chain (following stacking contexts)
is marked as having a descendant needing repaint. When stacking
contexts changed, we failed to maintain the descendant bits on the new
ancestor chain.
Bug: 1323016
Change-Id: I8a27b180b6a468a5107edf0fed1008a1d00e8753
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3632833
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001525}
--
wpt-commits: e44c9f21d22b42534cd71cd47260aaeec7504ad9
wpt-pr: 33996
Automatic update from web-platform-tests
[aspect-ratio] Only transfer min/max block-sizes if inline-size is auto.
Previously we'd universally transfer min/max block-sizes. This was
incorrect when we have an explicit main inline-size specified.
The spec says:
"This transferred minimum is capped by any definite preferred or maximum
size in the destination axis".
This patch has the same effect, by just not transferring if we have a
definite main inline-size.
Bug: 1320043
Change-Id: I570df533ec1b247b5890c0cd432cdf310db6a60c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3636115
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001512}
--
wpt-commits: 3d0650560de262882e8836a5295e42ac048d403c
wpt-pr: 34014
Automatic update from web-platform-tests
Replace cached ::first-line style from getComputedStyle
getComputedStyle may cache a ComputedStyle when requesting ::first-line
compared to which style should be used when the line is laid out. Make
sure we overwrite the cached one when the applied ::first-line style
originates from a parent block.
Bug: 1323201
Change-Id: Ief4ab7d07c751d7de339bbef3e6b839a48b6fddf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3629301
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001462}
--
wpt-commits: 4c7be82200fe3118d8fea0860ec26831350c2264
wpt-pr: 34002
Automatic update from web-platform-tests
[@container] Walk ancestry if ::first-line style is null
HasPseudoElementStyle may return true even if the element does not
currently apply any ::first-line rules because we
SetHasPseudoElementStyle when only container queries fail.
If we get a null ComputedStyle for an element which returns true for
HasPseudoElementStyle(kPseudoIdFirstLine), continue to walk ancestors to
look for the ::first-line style.
Bug: 1273913
Change-Id: I87b7f9c04f818f2d9c82c6eb417b81465f15d913
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3629362
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001435}
--
wpt-commits: 9456ecd8ee24fde91ae592673deeaed7cc5255b5
wpt-pr: 33992
Automatic update from web-platform-tests
Fix fragmentation freeze at tall trailing fieldset border.
The legend may stretch the fieldset border-box block-size, so that we
may have to override the block-size constraining CSS properties, to
encompass the legend in the fieldset. This should of course result in
the same override at every fragment, since ComputeBlockSizeForFragment()
works on total / "stitched" block-sizes.
Bug: 1323250
Change-Id: I48aec9a308cff40d19127e6a5a2dcc69abcedb41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3634342
Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001406}
--
wpt-commits: bc57edee8d7bf20f943f3bf41f9f86df0c5792e5
wpt-pr: 34003
Automatic update from web-platform-tests
Ignore Early Hints for <embed> and <object>
Early Hints for <embed> and <object> are already ignored even
without this CL as we check FrameTreeNode::GetParentOrOuterDocument(),
but we should have an explicit check for <embed> and <object> so that
we won't handle Early Hints for these navigations when we allow
Early Hints for sub frames in the future.
Bug: 1305896
Change-Id: Ifd077e2fabbc6403bf94577183d542dd2cde4221
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3631786
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001390}
--
wpt-commits: 317f8cfa1df4d249ba5543ddbd4b22ab10c152b2
wpt-pr: 33988
Automatic update from web-platform-tests
Reland "Use mojo_base.mojom.ReadOnlySharedMemoryRegion in device sensors."
This is a reland of commit 076ef25936e7142c67e21d9295dd92a139164e71
Original change's description:
> Use mojo_base.mojom.ReadOnlySharedMemoryRegion in device sensors.
>
> Unfortunately, the CL largely relies on using static_cast<const T*>
> instead of the safer GetMemoryAs<T> helper, since GetMemoryAs<T> requires
> that device::SensorReadingSharedBuffer is trivially copyable.
>
> Bug: 1306363
> Change-Id: I91d048450bf7ba341065e6175c9928be34e45946
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3621355
> Commit-Queue: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Reilly Grant <reillyg@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1000672}
Bug: 1306363
Change-Id: I49429e22aefc166d4dd254bbcf4eb826f9388db8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3632845
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001294}
--
wpt-commits: c5b428f15acfb17fe59b5a6f04a21c288a76ed36
wpt-pr: 33985
Automatic update from web-platform-tests
WebKit export of https://bugs.webkit.org/show_bug.cgi?id=240109 (#33999)
Add tests for `:modal` pseudo class
--
wpt-commits: d81f04acd4371d2939c7a30a090c9af913165874
wpt-pr: 33999
Automatic update from web-platform-tests
Add data URL worker IDBFactory opaque origin tests
These tests verify that IDBFactory methods that should
throw in opaque origin contexts correctly do so when
called from data URL dedicated and shared workers.
Bug: None
Change-Id: I1a7e806ac464d6de1932d9952072217a9ee91bbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3631352
Commit-Queue: Andrew Williams <awillia@google.com>
Reviewed-by: Ari Chivukula <arichiv@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001141}
--
wpt-commits: a88bca6c315aedaf20f1dc08f67fafe97d133509
wpt-pr: 33995
Automatic update from web-platform-tests
[TableFragmentation] Paint section/row backgrounds in cells correctly.
This correctly calculates the part-rect when fragmentation is present.
We use the OffsetInStitchedFragments to currently get the part size,
and offset, and use that to correctly paint the table section/row
backgrounds in the cell.
There shouldn't be any significant performance delta due to this patch.
Bug: 1078927
Change-Id: I05eb09e9221005c4da9404508317c1bf99687cce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3632829
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001100}
--
wpt-commits: 548d0a6be16f8350f117959c3a62fcf97c77414e
wpt-pr: 33975
Automatic update from web-platform-tests
Revert "Avoid unnecessary calls to paint invalidation."
This reverts commit 8bee5e4363e8cb5981d5a2a24b9533f4851a6dc0.
Reason for revert:
crbug.com/1291090
crbug.com/1323173
Original change's description:
> Avoid unnecessary calls to paint invalidation.
>
> Previously, any background color change during style resolution
> triggered paint invalidation regardless of whether the change is
> triggered by a composited animation. We now check if the color change
> has a native paint worklet before deciding if paint invalidation should
> be performed. In the event of a main thread background-color animation,
> we prevent spinning needlessly on building a native worklet paint image
> by caching whether the animation can be composited.
>
> Bug: 1301961
>
> Change-Id: I02a9b33267592590321af6d6c0e4da7cfbee2cc9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3542797
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Commit-Queue: Kevin Ellis <kevers@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1000090}
Bug: 1301961
Change-Id: Idc764b461410adc655e158af499130c195dd770f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3635297
Commit-Queue: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001026}
--
wpt-commits: 2bc981110402ce8c1e21b6a70d7fdb00518ee748
wpt-pr: 33993
Automatic update from web-platform-tests
[TableFragmentation] Paint column backgrounds correctly when fragmented.
This correctly calculates the columns-rect when fragmentation is
present. Instead of relying on the table-grid-rect - union the section
fragments of the table.
Typically this will be relatively fast, as tables typically only have
one fragment, and one section as a child of that fragment.
Bug: 1078927
Change-Id: I10c293ea0b5f307342efe83761fc4257b316848b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3632008
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001001}
--
wpt-commits: 7b52d2dc957de1c4168f324828a46208ee40bc45
wpt-pr: 33974
Automatic update from web-platform-tests
[@container] Resume recalc during reattach for non-rendered elements
If we skip the style recalc of some container, then we must immediately
resume that recalc if we find out during AttachLayoutTree that we're
not going to enter NGBlockNode::Layout after all. We already do this
in most cases, but not for non-rendered "leaf-nodes" in the
AttachLayoutTree traversal.
Marking for reattach is normally not allowed *during*
AttachLayoutTree, so an exception is added for this here using
AllowMarkForReattachFromRebuildLayoutTreeScope.
Also DCHECK whether or not reattach is allowed (StyleEngine:
MarkReattachAllowed) more eagerly, to make testing easier.
Fixed: 1321471
Change-Id: I539b0394e934de3759608eb0d55b0071416eadea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3629202
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1000959}
--
wpt-commits: d955c3e08db86d4cbe725d5f980635e7547c92bc
wpt-pr: 33966
Automatic update from web-platform-tests
Support overflow:clip on SVG
LayoutSVGRoot::ShouldApplyViewportClip to check overflow:clip
Bug: 1249247
Change-Id: I68694b82e0cb6f673873c88504428f897a3cb11b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3466885
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Shanmuga Pandi M <shanmugapandi@google.com>
Cr-Commit-Position: refs/heads/main@{#1000944}
--
wpt-commits: f76d415fdca714ad9654d456d2ef2d3cb7de33c3
wpt-pr: 33942
Automatic update from web-platform-tests
Update accessibility subtree when an event listener is removed
If an object was included in the accessibility tree solely due to an
event listener which was just removed, that object will be marked as
dirty and subsequently as ignored. When BlinkAXTreeSource::GetChildren
is then called due to serialization of updates and events, the parent of
that now-ignored object will have a child it should not and a DCHECK
will fail.
This commit solves that problem by calling ChildrenChangedOnAncestorOf
if the event listener was removed on an existing AXObject. Doing so
causes the accessibility tree to be updated prior to serialization of
updates and events. It includes an additional change and test from
crrev.com/c/3608668.
AX-Relnotes: N/A
Bug: 1319933
Change-Id: Ibb4b78d480d940c8274db75b3739cda0e253933e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3614009
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Joanmarie Diggs <jdiggs@igalia.com>
Cr-Commit-Position: refs/heads/main@{#997215}
--
wpt-commits: 31d0d369a16ad9200fc99be8c0517f1a0bc6e1cc
wpt-pr: 33991
Automatic update from web-platform-tests
Set fragment index to 0 when hit-testing in non-fragmented container.
Set the fragment index to 0, instead of leaving it at WTF::kNotFound,
when AppendSingleFragmentForHitTesting() has no container_fragment
specified. container_fragment is nullptr as an optimization, when
the container only has one fragment. See near the end of
HitTestLayerByApplyingTransform().
Bug: 1321302
Change-Id: Ibf6bfce2308229030304d99588defd9494ec0298
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3620315
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1000919}
--
wpt-commits: d18cf39d92d0116ae11a6aa034d9fe2f753ce304
wpt-pr: 33894
Automatic update from web-platform-tests
Ignore forced breaks in OOFs during initial column balancing.
The main layout machinery doesn't support resuming after breaks inside
OOFs. We rely on special-code in NGOutOfFlowLayoutPart and
NGSimplifiedOOFLayoutAlgorithm invoked at the outermost fragmentation
context root for this to work. However, during initial column
balancing, we don't treat OOFs specially, but this isn't implemented for
the main machinery.
To fix this correctly, we would have to store the incoming break token
for an OOF in NGPhysicalOutOfFlowPositionedNode and do some more stuff
in NGOutOfFlowLayoutPart. But I don't think it's necessary at this
point, so just make sure that we never break inside OOFs in the initial
column balancing pass.
Bug: 1322319
Change-Id: I062a0ca2f57d24bd877a74e20cdb70dcff33ad20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3629358
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1000918}
--
wpt-commits: d09850ce75db0e9b0fde8e1e27d102faab0091e7
wpt-pr: 33964
Automatic update from web-platform-tests
Added a WPT-test for connecting a TMST to a video element.
Marked as skipped because it is currently crashing due to the required
functionality in TransferredMediaStreamTrack not yet being implemented.
Bug: 1288839
Change-Id: I011f156c944a000ef1b5a8f683462216ccf67ad4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3623900
Commit-Queue: Tove Petersson <tovep@chromium.org>
Reviewed-by: Tony Herre <toprice@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1000891}
--
wpt-commits: f0e16e31ab532deac9d4a3aa15b9c5098a43cdf4
wpt-pr: 33926
Automatic update from web-platform-tests
html: Change selection-not-application-textarea.html test to accommodate (#33961)
platforms with different default selection direction values.
The test calls setSelectionRange(start, end [, direction]) API with
the direction argument ommitted. As per spec at
https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#textFieldSelection,
If the direction is omitted, it will be reset to be the platform default (none or forward).
The existing test script expects the direction to be "forward" only.
This patch updates the test script to be in line with spec.
--
wpt-commits: c680b63714bb17748a049c9bcb37878b41ffc9ff
wpt-pr: 33961
Arthur Sonzogni
ziransun
Delan Azabani
Robbie McElrath
Mike Wasserman
Jordan Bayles
Mason Freed
Philip Jägenstedt
moz-wptsync-bot
Mustaq Ahmed
Tim Nguyen
Xiaocheng Hu
Philip Rogers
Ian Kilpatrick
Rune Lillesveen
Noam Rosenthal
Sam Sneddon
Morten Stenshorne
Kenichi Ishibashi
Oriol Brufau
Daniel Cheng
Andrew Williams
Kevin Ellis
dependabot[bot]
Anders Hartvoll Ruud
Shanmuga Pandi M
Joanmarie Diggs
Philipp Hancke
Tove Petersson
Fergal Daly