<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [meta] positionIsOffsetInAnchor should only accept text nodes"
href="https://bugs.webkit.org/show_bug.cgi?id=63040#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [meta] positionIsOffsetInAnchor should only accept text nodes"
href="https://bugs.webkit.org/show_bug.cgi?id=63040">bug 63040</a>
from <span class="vcard"><a class="email" href="mailto:yosin@chromium.org" title="yosin@chromium.org">yosin@chromium.org</a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=63040#c7">comment #7</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=63040#c6">comment #6</a>)
> > >> 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)</span >
Thanks for explanation. So, you want to avoid computing node index. But, why not use RangeBoundaryPoint?
It seems AnchorType introduces complexity in Position class.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>