You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue might be better labeled, inconsistent return of getSelection().
Here is an old w3c/editing task force issue that seems to be indicating the same thing: w3c/editing#156
In the CM6 unit test in question, the call to window.getSelection() returns the text node rather than the div node. The test passes for Chrome and Firefox on my macOS system.
The unit test actually tests seven different selections and by commenting out the rest so just one at a time is tried, one can see four are returning the text node itself rather than the expected text node's parent. Those four are shown with an extra arrow comment here.
Issue might be better labeled, inconsistent return of getSelection().
Here is an old w3c/editing task force issue that seems to be indicating the same thing: w3c/editing#156
In the CM6 unit test in question, the call to window.getSelection() returns the text node rather than the div node. The test passes for Chrome and Firefox on my macOS system.
The unit test actually tests seven different selections and by commenting out the rest so just one at a time is tried, one can see four are returning the text node itself rather than the expected text node's parent. Those four are shown with an extra arrow comment here.
In fact, if window.getSelection() is called immediately after the test's requireFocus() call to setup things, the difference can also be seen.
The text was updated successfully, but these errors were encountered: