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

As for https://github.com/w3c/editing/issues/163#issuecomment-307338972, that seems to have been a multicell table, right?

I have been thinking about this over the last few days. I think treating one-cell single-character tables differently than other tables must at some point of time having had to do with such tables being used for styling of letters or words. Or someone imagined that it could be used for that, or somehow those kinds of tables were thrown into the same category as elements that are typically used for styling... 

At any rate, I cannot think of a good example where it would make sense to use a table for the purpose of styling as of 2018. And if we accept that JS editors will be either be executing editing operations entirely by themselves or do at least take over a great part of these editing operations... the one thing that is not very welcome by those writing these editors is unpredictable or surprising behavior on the part of browsers. Treating single cell tables differently than other tables is an example of really surprising behavior in my view.

So yes, although I really cannot see the purpose of single-cell tables, I agree with you, in those cases where they do exist, browsers should treat them like any other table.

As for behavior when selecting the entire table and deleting it vs selecting all contents of a table and then deleting, I feel there needs to be some type of visual distinction between the two types of selections. If there is no distinction, then it should behave according to what the most common case is, which I would guess to be to delete the entire table. 

-- 
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-388964965