Closed Bug 2021167 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 58272 - Disconnect OpaqueRanges on text control removal and input type changes

Categories

(Core :: DOM: Core & HTML, task, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
150 Branch
Tracking Flags:
Tracking Status
firefox150 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Stephanie Zhang <stephanie.zhang@microsoft.com> wrote:

Disconnect OpaqueRanges on text control removal and input type changes

Ensure OpaqueRanges are properly disconnected when a text control is
removed from the document or when an input element's type changes. This
prevents stale ranges from persisting after the element is no longer
part of the document tree.

Bug: 421421332
Change-Id: I76aee678bbd435d6a0384a5e801c02a6277c7e40
Reviewed-on: https://chromium-review.googlesource.com/7596769
WPT-Export-Revision: f106c84fdbfa33d516c4c1f83a99302fa4cf9b07

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 17 subtests

Status Summary

Firefox

OK : 1
FAIL: 17

Chrome

OK : 1
FAIL: 17

Safari

OK : 1
FAIL: 17

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /dom/ranges/tentative/OpaqueRange-auto-disconnect.html [wpt.fyi]
    • OpaqueRange disconnected on element removal (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • All OpaqueRanges disconnected on element removal (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • Element accepts new OpaqueRanges after re-insertion (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on ancestor removal (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on implicit removal via innerHTML (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • No error when element removed after manual disconnect (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected when element adopted into another document (textarea): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on element removal (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • All OpaqueRanges disconnected on element removal (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • Element accepts new OpaqueRanges after re-insertion (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on ancestor removal (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on implicit removal via innerHTML (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • No error when element removed after manual disconnect (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected when element adopted into another document (input): FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on input type change to "color".: FAIL (Chrome: FAIL, Safari: FAIL)
    • OpaqueRange disconnected on input type change to "search".: FAIL (Chrome: FAIL, Safari: FAIL)
    • Input accepts new OpaqueRanges after type changes back to text.: FAIL (Chrome: FAIL, Safari: FAIL)

https://hg.mozilla.org/mozilla-central/rev/5de9ebbc8cde
https://hg.mozilla.org/mozilla-central/rev/c1744ccbeb9c

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