Style not cleared at start position

Hi,

Is there a fix or a workaround for the issue in this post? I see the same problem in Ckeditor 3.6.1 as well. FF & IE behaves one way, while safari and chrome behaves differently. I see in the demo (http://ckeditor.com/demo) as well. For example.

If I type "This is a test" in the editor, select the line and change the font style to "Comic Sans MS". Then place the cursor at the end of the line and start deleting using 'backspace'. When the character at the beginning of the line is deleted,
- In FF, the font style in the drop down (in the toolbar) remains "Comic sans MS". When I start typing again, the text is formatted with font "comic sans MS".
- In Safari & Chrome, when the character at the beginning of the line is deleted, the font in the drop-down changes to Arial, but when I start typing, the text is formatted with "Comic Sans MS".

Thanks
Anand

Unfortunatelly, the problem here is that the text being edited is quite flat for us but the browser has to map it to the DOM tree structure. Every browser can do it in its own way.

See https://dev.ckeditor.com/ticket/7796#comment:4 and https://dev.ckeditor.com/ticket/7796#comment:8 for discussion on another symptom of this problem.

Thanks for the reply. I understand that each browser does its own way. The last comment on that ticket (7796) says that it works well in v4. Does this mean that the issue is fixed in ckeditor version 4?

What is more confusing is that in Safari and Chrome, the state of the buttons/selection (style, font etc) is different than the actual style applied to the text. In my example, when the last character in the line is deleted, the font in the drop-down box in the toolbar changes to "Arial". When you start typing some text again, the font selection in the toolbar remains "Arial", but the actual style applied is "Comic Sans". Is this a bug in ckeditor?

Anand

I'm not sure what the last comment means as the link in this comment leads to gitweb.cksource.com which I can't connect to (host not found).

If the state of buttons/selection is different than the actual style being applied then it's definitely a bug.

BTW I think I wasn't quite precise in the previous post. By text<->DOM mapping I meant the mapping of navigation in text to navigation in DOM.

E.g. if we have

<i>he<b>ll</b></i><b><i>o</i></b>

yes, the state of the button/selection is different than the actual style being applied. Is there a defect or should I open a defect? Do you know if there is a fix?

Thanks
Anand