Chromium Bug: Selection API stale after DOM replacement in contenteditable

This page runs the repaired selection strategy. The test scenarios are identical to the raw control, but every selection read goes through currentRange(), which first verifies ownership and then applies the narrow zero-rect repair before returning a range.

Use it after you find a failing raw scenario. If the workaround applies cleanly, the marker should stay green and the log should note that the stale selection was repaired instead of remaining stuck at offset 0.

currentRange() polled every 2 s: