[Webkit-unassigned] [Bug 63040] [meta] positionIsOffsetInAnchor should only accept text nodes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jun 28 22:52:57 PDT 2015


--- Comment #8 from yosin at chromium.org ---
(In reply to comment #7)
> (In reply to comment #6)
> > >> What do you mind to represent child node w/o PositionIsOffsetInAnchor?
> > > Performance.
> > 
> > Oops, my question is unclear.
> > How do we represent a position at child node w/o PositionIsOffsetInAnchor?
> > Use LegacyEditingPosition?
> Use BeforeChildren, AfterChildren, BeforeAnchor, or AfterAnchor (for the
> latter two, you need to change the anchor node since we're no longer
> anchoring at the parent)

Thanks for explanation. So, you want to avoid computing node index. But, why not use RangeBoundaryPoint?
It seems AnchorType introduces complexity in Position class.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150629/746c04f9/attachment-0001.html>

More information about the webkit-unassigned mailing list