Open Bug 2009323 Opened 1 day ago Updated 1 day ago

`RangeBoundaryBase` should be initialized only with a valid point

Categories

(Core :: DOM: Selection, task)

Product:
Core
Component:
DOM: Selection
Type:
task

Tracking

()

Status:
ASSIGNED

People

(Reporter: masayuki, Assigned: masayuki)

References

(Depends on 2 open bugs)

Details

The constructors of RangeBoundaryBase just warn it when it's initialized with an invalid set of container/offset/child. Even it can become invalid after mutations, the initial boundary should be always valid if it points to a child (i.e., not a static range). Then, we can guarantee that nsRange has only valid boundaries.

You need to log in before you can comment on or make changes to this bug.