Closed
Bug 795325
Opened 13 years ago
Closed 12 years ago
Delete on nested list selection may destroy the list
Categories
(Core :: DOM: Editor, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: fredck, Unassigned)
Details
Attachments
(1 file)
|
167 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4
Steps to reproduce:
1. Open a page with the following HTML (sample attached):
<!DOCTYPE html>
<html>
<body contenteditable="true">
<ul>
<li>One
<ul>
<li>Child 1</li>
<li>Child 2</li>
</ul>
</li>
<li>Two</li>
</ul>
</body>
</html>
2. Place the caret at the start of the first (One) item.
3. Hit SHIFT+DOWN, so select the item.
4. Hit DEL to delete it.
The list structure will be broken as Child 1 will move after Child 2.
Related CKEditor ticket:
http://dev.ckeditor.com/ticket/8829
|
||
Comment 2•13 years ago
|
||
Thanks Fred for your report! Is this a regression?
(In reply to Ehsan Akhgari [:ehsan] from comment #2)
> Thanks Fred for your report! Is this a regression?
I don't think so. It is TC that appeared at our side a few months ago. We figured out that it is hard to workaround, so we're reporting it just now.
|
|
||
Comment 4•13 years ago
|
||
(In reply to comment #3)
> (In reply to Ehsan Akhgari [:ehsan] from comment #2)
> > Thanks Fred for your report! Is this a regression?
>
> I don't think so. It is TC that appeared at our side a few months ago. We
> figured out that it is hard to workaround, so we're reporting it just now.
How important is this for the CK Editor? If it's very important, I can try to get it fixed soon.
Attachment #665903 -
Attachment mime type: text/plain → text/html
(In reply to Ehsan Akhgari [:ehsan] from comment #4)
> How important is this for the CK Editor? If it's very important, I can try
> to get it fixed soon.
Generally speaking, all browsers are doing well with editing, when it comes to the "asdsadas" tests. Issues like the one in this ticket are instead very common but unfortunately get little attention, usually. People feel very depressed when they hit them though.
At the same time, there are few things that we (CKEditor) trust that browsers will do well, just because they're impossible/hard to be implemented by us. Selection, caret control and keystrokes behavior are some of these features. So, when a browser fails on these base infrastructural aspects, we get depressed.
So, what you have: a bunch of depressed and disappointed people :)
But we'll never tell you guys what you should do. All I can tell you is that this issue comes from a customer of us, which extensively tests CKEditor on all browsers, including Firefox. They're giving us important feedback so we do our best to make the editing world better. This is an important issue for them, so it is automatically an important issue for us. They deserve this kind of attention.
|
|
||
Comment 6•13 years ago
|
||
I would be more than happy to help you guys at least with the editor related issues in Firefox that you deem important! :-)
Aryeh, can you please take a look at this? Thanks!
Assignee: nobody → ayg
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
||
Comment 7•13 years ago
|
||
Sorry for the delay -- I was away for a week, so I couldn't look at this right away.
I can reproduce the bug on Firefox 15.0.1, but it seems to be fixed already in 18.0a1 (2012-10-08). Could you download a nightly from http://nightly.mozilla.org/ and test it there? If it works there, it must have been fixed in either 16 or 17 or 18, and the fix will make it to the release channel in zero/six/twelve weeks accordingly. (Firefox 16 is being released today, 17 will be in six weeks, 18 will be in twelve weeks.)
If that's the case, I guess there's nothing more to do here. Thanks a lot for the report, though! Please be sure to report any other Firefox bugs that are important to you; this sort of minor thing often isn't hard for us to fix. Sometimes it is, but it's always worth reporting.
|
|
||
Comment 8•12 years ago
|
||
Resolving WORKSFORME because it seems to be fixed in latest Firefox, per comment 7. Please reopen if you're still seeing it.
Assignee: ayg → nobody
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•