IE Standards Mode: Incorrect selection & range produced when clicking to the right of a <br />

[Scott McNaught]

For the first 500ms after clicking to the right of a <br />, IE produces a range at the wrong spot.

To see the problem, edit plugins/selection/plugin.js. In IEs getNative(), add: this.document.$.selection.createRange().select(); so it looks like:

CKEDITOR.env.ie ?
	function()
	{
		this.document.$.selection.createRange().select();
		return this._.cache.nativeSel || ( this._.cache.nativeSel = this.document.$.selection );
	}

Then open ckeditor, and set the HTML to:

<p>Line 1<br />
Line 2</p>

Click to the right of the Line 1 / the <br />. The caret will move to the start of Line 2, thus proving that the IE range created is wrong.

Some notes:

• 500ms after the click, calling getRange() code will produce the range at the correct position.
  
• The range produced is definately wrong and at Line 2. In getBoundaryInformation(), the compareEndPoints() check will show that the selection is after the <br />
  
• The issue is also present after the editor loses focus, and regains it (ie - when using a RichCombo).
  
• This issue doesnt happen when focussing using right click / context menu.
  
• The issue flows through and makes the w3 range wrong too

[Garry Yao]

@Scott:Did you see any usability issue with this? As we would just follow the 'final decision' of IE since other browsers agreed with that also, and most importantly, it's in expectation.

[Scott McNaught]

Hi Garry,

Its not really noticed in normal CKEditor.. Its mainly a problem when you start developing custom stuff.

---

An example though in CKEditor... Set the source to:

<p>Line 1][<br />
</p>

... where the users selection is at ][

Then change the font colour or font background/highlight colour. You will notice that the caret moves to the start of the next line.

---

See back to my "Notes" section above where I say "- The issue is also present after the editor loses focus, and regains it (ie - when using a RichCombo)." When interacting with the toolbar and changing the focus (i assume for accessibility), the refocus suffers the "500ms problem".

Im not sure what you meant by "As we would just follow the 'final decision' of IE since other browsers agreed with that also, and most importantly, it's in expectation."

Cheers,

Scott

[Frederico Caldeira Knabben]

Milestone CKEditor 3.x deleted

[Jakub Ś]

I was not able to reproduce this in latest CKEditor 3.6.4.