We should fix it to be not doing anything, if not inside of a sub list.
9129.patch​ (1.2 KB) - added by Garry Yao 7 years ago.
9129_2.patch​ (3.5 KB) - added by Garry Yao 7 years ago.
9129_3.patch​ (8.1 KB) - added by Garry Yao 7 years ago.
9129_4.patch​ (7.8 KB) - added by Garry Yao 7 years ago.
9129_5.patch​ (8.7 KB) - added by Garry Yao 7 years ago.
The propose behavior introduce an exception that when list item is empty instead, it will perform an outdent, this matches actually the behavior of most browser impl, and our enterkey behavior as well.
If I deleted the entire "Item 1" with BACKSPACE (leaving it empty), it will outdent if BACKSPACE again?
If yes, this is wrong. We can do so only if we're inside an empty "list", not an empty "list item".
I can confirm that no browser could agree with the above TC in 7, Fx and Webkit both merges the list item with previous line.
As for 6, empty list item with nested list are not into this case, but I see browsers have problem removing this last char (empty the item) even, so it's blocking the test right now.
This would be in fact be the user's way to "exit from the start" of a list structure.
In any case the impl would not be trivial anymore, so we'd avoid rushing with it at the moment.
I don't really care about the default browser behavior. I think we can put our heads at work and come with a solution that is based on reasonable arguments instead.
The idea of making it outdent only if there is no sublist is acceptable as well. I'm still worried that users may few confused because sometimes it works, sometimes it doesn't (when having sublist). In any case, this is a risk we can take for now. I'm ok to proceed that way.
I've noticed that the behavior has changed in trunk with  (at least in Firefox), when talking about the scenario when list is at the top of the content.
In 3.6.4 SVN: nothing happens when backspace is pressed.
The result from 3.6.3 is more intuitive imho.
As originally reported in ​this comment, the whole list is now deleted in Opera (I've filled a ticket for it: #9158). It makes this particular ticket even more important.
No content before to merge with, e.g. at the start of doc - deconstruct list, try to avoid the "doing nothing" behavior.
I think there was a misinterpretation on our discussion. The BACKSPACE key must have no action if the list has a sublist. In all other cases, the list gets transformed into a paragraph.
I've updated the tests to reflect this.
As #9152 is highly related to this ticket, I'd merge the review request here.
New patch is to adjust the behavior (to not outdent) when sub list is pertained, but instead of doing nothing in such case, we'd just move the cursor to the desired direction indicated by the keystroke (backward for BACKSPACE, and forward for DEL).
This can be verified in many browsers, thus it makes sense for us to reuse it when we dont want sub list to be merged.
I'm "ok" with the selection positioning on the "do nothing" case. Let's see how it'll be accepted by our users.
There are some bad decisions on the tests though.
Why "list2b_del_before" should behave differently than "list3_del_before"? We're just breaking an important current feature with that.
Additionally, there are two tests that have been changed but they're certainly correct.
I've updated t/9129 on tests to reflect this.
Updated the patch to match the current TC set.
Do you confirm that the current two reds that we have are just a matter of updating the tests?
If yes, please do so before putting it on review again.
I have these reds with Chrome only. With FF it is ok.
At first glance it's a test problem, but it's instead caused by missing filling char when the paragraph is empty, so I had to patched once more the filling char logic.