Resolve inconsistency between DOM and Flat tree position canonicalization |
||||
Issue descriptionThere are some cases where we canonicalize a Position to a non-null VisiblePosition, but the position in fact does't participate in the flat tree, and hence, should be canonicalized to null. Example: <div id=host> <span id=anchor>foo</span> bar </div> where DIV#host is a shadow host, and span#anchor is not distributed into the shadow DOM. In this case, Position (SPAN#anchor, Before/AfterAnchor) doesn't participate in the flat tree, and hence, should be canonicalized to null. We need to fully understand the implementation of |CanonicalPosition| to resolve this issue.
,
Jul 28 2017
Found another case reproducing the inconsistency, but in the other way that flat tree canonicalization gives non-null result but DOM tree canonicalization gives null. Use the test case in https://bugs.chromium.org/p/chromium/issues/detail?id=745501#c11. After triple clicking under the table, the frame selection is set to start = TABLE@0 end = TABLE@AfterAnchor In selection canonicalization, we get VSInFlatTree being null but VSInDOMTree not null.
,
Jul 29 2017
,
Jan 10 2018
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by xiaoche...@chromium.org
, Jun 5 2017