Re: [w3c/editing] Should deleting cell's content on a table inside a contenteditable area imply the whole table has to be deleted ? (#163)

Btw, I didn't try all your tests, but in Firefox 59 on Linux, in case 2, I get different results. And the results also differ between using backspace and delete in that case. 

In case 4, I just now realize that the deletion is eating an extra space backward. It should probably say "before ", but the result is "before". This extra space is there initially, then disappears and doesn't seem to come back. If one tries to type a single letter ("x") at the end of it "before |" it turns into "beforex". It is not present on other browsers.

Another test that you did not include -- select from the beginning of the first table cell to the end of "after" fails because it refuses to select more than the table contents. And even that it does rather badly -- if I accidentally move the mouse a bit downward during the selection, the selection goes no further, even if I move the mouse back up to try to select the remaining table cells.

These sort of selection issues are more problematic because they force JS editors to write weird work-arounds to get their editors to work properly, or write their own selection system. I think we have higher chances of getting the built-in selections good enough where most JS editors can rely on them than getting full agreement on all default editing operations.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/163#issuecomment-388110539