Closed Bug 1767253 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 33894 - Set fragment index to 0 when hit-testing in non-fragmented container.

Categories

(Core :: Web Painting, task, P4)

Product:
Core
Component:
Web Painting
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
102 Branch
Tracking Flags:
Tracking Status
firefox102 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 33894 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/33894
Details from upstream follow.

Morten Stenshorne <mstensho@chromium.org> wrote:

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/3620315
WPT-Export-Revision: 24ddbc86e5a9c5404de3aa4928c65af207e6f9c4

Component: web-platform-tests → Web Painting
Product: Testing → Core
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0dbeeb03e3cb
[wpt PR 33894] - Set fragment index to 0 when hit-testing in non-fragmented container., a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/0dbeeb03e3cb

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox102: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in before you can comment on or make changes to this bug.