Opened 10 years ago
Last modified 10 years ago
#12312 confirmed Bug
[FF] An extra BR added to the elementspath
Reported by: | Marek Lewandowski | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 3.5.1 |
Keywords: | Cc: |
Description
When we'll make a selection of an "end of line" (ofc it's not really an EOL) elements path will report an extra BR, which is not a part of end-user content, but seems to be a part of our internals.
- open any sample with CKEditor (i.e. samples/replacebyclass.html)
- use following source
<p>foo</p> <p>bar</p> <p>baz</p>
- switch back to wysiwyg mode
- place caret at the begining of second line
^bar
- expand selection to one character left (
shift + left arrow
)
Expected result:
Elements path should have following members: body p
Current result:
Elements path contains an extra br
: body p br
Change History (3)
comment:1 Changed 10 years ago by
Version: | → 3.5.1 |
---|
comment:2 Changed 10 years ago by
Status: | new → confirmed |
---|
After consulting this with @Reinmar I'm confirming this issue. These br tags it is not part of data but internal code so they should be hidden from user.
comment:3 Changed 10 years ago by
This issue will also be reproducible on IE11 and on Webkit/Blink if line was typed manually (because it was earlier empty so it had bogus <br>).
I'm not sure whether we should hide only bogus brs or all brs at all - it's odd but in such case:
<p>foo[<br>]bar</p>
Is really selected. But it's not an image either, which selection is clearly visible for users. But for sure filtering out all <br>s will be simpler and faster.
Problem can be reproduced from CKEditor 3.5.1 rev. [6373]. Fix in #7041 was Firefox specyfic so this issue is FF specyfic too.
I'm still however unsure whether element's path should hide this tag or not?