Opened 13 years ago

Last modified 8 years ago

#8382 confirmed Bug

IE : PageUp & PageDown not working — at Version 7

Reported by: Satya Minnekanti Owned by:
Priority: Normal Milestone:
Component: General Version: 3.0
Keywords: IBM IE Cc: Damian, Teresa Monahan, rschnorenberg@…, giorgio

Description (last modified by Jakub Ś)

To reproduce the defect:

  1. Enter content in CK Editor that spans multiple pages.
  1. Press PageUp button.

Expected Result: Cursor in editor body moves one page up.

Actual Result: Cursor goes to start of page content.

  1. Press PageDown button.

Expected Result: Cursor in editor body moves one page down.

Actual Result: Cursor goes to end of page content.

Tested against IE8, IE9 & IE10

Change History (7)

comment:1 Changed 13 years ago by Jakub Ś

Status: newconfirmed
Version: 3.0.2

Paging has never worked in IE (7-9)

Effect described by @satya has been reproducible from CKE 3.0.2.

comment:2 Changed 12 years ago by NicHolt

This is an M$ browser "feature" in IE7 onwards which only occurs when the element to be scrolled is contentEditable.

Here's a workaround, in the wysiwygarea plugin. It emulates scrolling up and dowm, rather than Page Up and Page Down - i.e. the caret is NOT moved. However, for those that prefer keystrokes to mouseclicks, it's a huge improvement on the M$ "feature".

if (env.ie && (env.ie7 || env.ie8)) {  // And IE9? though I can't test that
	var docEl = editor.document.$.documentElement;
	var scrTop = docEl.scrollTop;
	var scrHgt = docEl.scrollHeight;
	var winHgt = editor.document.getWindow().getViewPaneSize().height;
	
	if (keyStroke == 33) {  // Page Up
		docEl.scrollTop = Math.max(scrTop - winHgt, 0);
	}
	else {                  // Page Down
		docEl.scrollTop = Math.min(scrTop + winHgt, scrHgt - winHgt);
	}

	evt.data.preventDefault();
}
else {
	setTimeout( function ()
	{ 
		editor.getSelection().scrollIntoView();
	}, 100 );
}



comment:3 Changed 12 years ago by Garry Yao

Thanks for the feedback, we would plan the fix of this issue in V4 eventually.

comment:4 Changed 12 years ago by Jakub Ś

We had almost the same ticket reported and it was marked as won't fix - http://dev.ckeditor.com/ticket/6147#comment:2
Perhaps there will be a fix for it in v4 with usage of the idea reported by @NicHolt or some other trick but please keep in mind that browser will not be very helpful here.

comment:5 Changed 10 years ago by Rick Schnorenberg

Cc: rschnorenberg@… added

comment:6 Changed 10 years ago by Jakub Ś

#12549 was marked as duplicate.

I have checked this issue in native elements - iframe pointing to HTML5 page with body set to contenteditable="ture".

In IE8-10 there is no scroll. CKEditor works better as it at least moves the content to area where cursor is.

In IE11 there is a scroll but there are issues (same as in native environment) - you won't scroll on pageDown if you have focused an image in H1. I have also noticed that paging was blocked once you reach table.

comment:7 Changed 9 years ago by Jakub Ś

Description: modified (diff)
Keywords: IE added
Version: 3.0.23.0

#7956 was marked as duplicate.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy