Scroll Into View Bug When Breaking Large Content (FF)

[dshafik]

If you paste a large amount into the editor, where you end up with:

<p> some large text <br /> paragraphs aren't there anymore </p>

And you wish to put the paragraphs in to make it look like:

<p> some large text </p> <p> paragraphs aren't there anymore </p>

It will scroll the end of the second paragraph into view, which when the end is far enough away, will push the cursor off-screen, which can be confusing (why did I jump to the bottom?).

If you continue to type, it'll start typing where the cursor is, not where the eye is, scrolling that back into view.

The lines that cause the issue are fckenterkey.js lines 538/539:

source:FCKeditor/trunk/editor/_source/classes/fckenterkey.js@2136#L538

I initially just commented this out, but then when you want to put in a new paragraph at the end, it will not scroll that into view.

It seems to me that it should scroll when the paragraph is empty, but not otherwise, adding a FCKDomTools.CheckIsEmptyElement() will not work however, as we actually have:

<p> <br _moz_dirty=""> <br type="moz"> </p>

Some changes to the CheckIsEmptyElement() however will solve this (see patch).

This does not completely solve the issue. When pressing enter with an "empty" paragraph being add, it will work fine. When pressing enter with a non-empty paragraph following, it works fine so long as it's not at the bottom of the view area, because then it doesn't scroll and should.

This is a little better, but not complete. The best solution would be to move to the top of the paragraph, not the bottom. Is this possible?

• Davey

[dshafik]

Patch to partially fix enter key with following content odd movement

[arczi]

Could you try it with current version? It seems to be fixed.  http://www.fckeditor.net/demo

[dshafik]

This bug was reported against, and still exists in 2.6.3, as well as the latest revision (r2400)

[arczi]

I'm still not able to reproduce this bug in latest version. Please write more details.

[fredck]

Confirmed with FF3.

[martinkou]

Tested the new patch on Opera, Safari and Firefox 3. Works like a charm.

[fredck]

Fixed with [2565].