[Webkit-unassigned] [Bug 54535] Stop calling node() and deprecatedEditingOffset() in comparePositions

Tue Jun 19 10:45:10 PDT 2012

https://bugs.webkit.org/show_bug.cgi?id=54535

--- Comment #6 from Shinya Kawanaka <shinyak at chromium.org>  2012-06-19 10:45:08 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > I'm now thinking "position after img" and "position before br" is different in some meaning. When inserting something between img and br, those position becomes different apparently.
> 
> I don't think that makes sense. They're identical DOM positions. We should figure out why we have to treat them differently and fix that problem.

As we (shinyak and rniwa) talked on 18 Jun 2012, they are the same DOM positions, but when inserting some elements between <br> and <img>, they become another position.
Maybe we should be careful about choosing the anchor node. Even though (br, after node) and (img, before node) are the theoretically same, there is a case that one is apparently more suitable than the other.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.