[IE] Cursor after table at the end of document in enterMode=BR

[Garry Yao]

Environment

IE8 standards, with enterMode = BR.

Reproducing Procedures

1. Load any of the sample page and fill the editor with the following contents:

   <table>
   	<tbody>
   		<tr>
   			<td>
   				text</td>
   		</tr>
   	</tbody>
   </table>
   

2. Click into the spaces after the table at the end of document.

• Expected Result: It's possible to have the cursor blinking there and start typing.
• Actual Result: Cursor stays as it is.

[Garry Yao]

WFM in IE6/7.

[Wiktor Walc]

The patch needs to be updated. Same problem with horizontal line and page break for printing.

[Sa'ar Zac Elias]

The patch needs to be updated. Same problem with horizontal line and page break for printing.

[Sa'ar Zac Elias]

There is now redundant NBSP in the content. Also, I don't see the problem is fixed for HR and page break for printing.

[Garry Yao]

Proposing a new approach for handling body padding in IE that eliminates placer holder text.

[Sa'ar Zac Elias]

Interesting approach;

• In IE, The approach doesn't work for me using enterMode=BR.
• In FF, double clicking on the element makes the cursor disappear.

[Garry Yao]

Replying to Saare:

• In IE, The approach doesn't work for me using enterMode=BR.

It actually works for IE with enterBr in obscurity, as the cursor is displayed at wrong position while once you start typing, inputed are placed at the correct place, I understand it's an usability issue, while fortunately it works just fine in enterP mode (with the help of autoParagraph).

[Sa'ar Zac Elias]

[IE] Create a table using the dialog. Write a letter. Press BACKSPACE 2 times. Note that the caret went to the last cell, and it's now again impossible to click beneath the table.

[Garry Yao]

WFM in IE8 (it's still possible to click beneath the table), in IE7 BACKSPACE removes the entire table instead.

[Sa'ar Zac Elias]

WFM now as well;

• If there is already a paragrpah above the div, it should not appear, as it only adds additional height with no benefits.
• [IE, enterMode=BR] Insert a table with lots of rows. Click beneath the table. Note that the editor scrolls to top, but places the caret "correctly" (comment:10). Type some text, note that the text goes into the last cell.

[Wiktor Walc]

IE8, I'm unable to type any content both by clicking below the table or using arrow keys to move down below the table.

Initial source:

<table border="1" cellpadding="1" cellspacing="1" style="width: 500px">
	<tbody>
		<tr>
			<td>
				one</td>
			<td>
				two</td>
		</tr>
		<tr>
			<td>
				three</td>
			<td>
				four</td>
		</tr>
	</tbody>
</table>

In FF 3.6.13 I do not see the cursor blinking, so it's not intuitive that I can type at this moment below the table.

In Safari the cursor is blinking, but all the content is lost after switching to source and a div element is visible in the elements path.

[Wiktor Walc]

The attached screenshot shows the problem with Safari: attachment:5479_4.png​

[Wiktor Walc]

Actually, why not simply add extra <br /> elements at the end of document when the last element is the one that is causing problems?

Note that at this moment it looks like the last two line breaks after the element which is causing problems are always removed from the source when switching to source mode. To reproduce, try the following and switch to source mode and back with enter mode br:

<hr />
<br />
<br />
<br />

[Garry Yao]

I understand the cursor stop blinking (or blinking at wrong position) might be counterintuitive, but I think user will still give it a try.

@wwalc The safari issue has been tackled with the last patch.

[Wiktor Walc]

Works better in Safari, but does not work with Opera.

[Garry Yao]

Opera problem and cursor blinking problem resolved with new patch.

[Wiktor Walc]

The position of the cursor in IE is still very confusing, I wouldn't dare typing seeing this: attachment:5479_6.png​

[Wiktor Walc]

I've reported in #6984 disappearing line breaks mentioned in comment:17.

Theoretically we could use <br> elements instead of <div> to add a line break after tables and horizontal rules. This extra BR tag could have a special attribute. Once finding such a <br> element at the end of the document we could simply remove it before switching to source mode. When finding such line break in the middle of the document, we would just remove the attribute from it.

[Sa'ar Zac Elias]

Both issues could be reproduced using a sample table:

<table border="1" cellpadding="1" cellspacing="1" style="width: 500px">
	<tbody>
		<tr>
			<td>
				&nbsp;</td>
			<td>
				&nbsp;</td>
		</tr>
	</tbody>
</table>

• In FF the bogus BR is not removed.
• Hit CTRL+A. Click on RTL icon. Click on the pad. Note that the paragraph is LTR while it should be RTL.

[Garry Yao]

Replying to Saare:

• In FF the bogus BR is not removed.

Caused by a bug of element::appendBogus, addressed in new patch.

• Hit CTRL+A. Click on RTL icon. Click on the pad. Note that the paragraph is LTR while it should be RTL.

Nice catch, the issue is now resolved in enterP/DIV, while it's difficult to featue smart text direction for enterBr though, we could leave it to be handled by later ticket.

[Wiktor Walc]

IE6, type some text below a table, press enter. See the screenshot.

[Garry Yao]

The IE6 issue is not part of this ticket, please apply the patch at #6992 before testing.

[Wiktor Walc]

Safari 5 @ win: clear all contents, click on an empty editing area with enter mode br.

Result:

TypeError: Result of expression 'last' [null] is not an object.
wysiwygarea/plugin.js, line 690.

[Frederico Caldeira Knabben]

There are two problems with this approach, which can be verified with Firefox:

• It's not anymore possible to place the cursor is a specific text position by clicking in the white-space following the text. Before the patch, when you click in the space bellow the middle of the text, the cursor is positioned in that precise point. After patch, it goes always to the end of the text.

• It's not anymore possible to drag things from outside the editor into the blank space following the text. This is a more serious thing, because I know that people is using this kind of drag-and-drop solution out there.

Considering this is an IE issue, shouldn't we come with an IE only solution at that point, instead of changing the behavior for all browsers?

[Garry Yao]

@Fred, I'm concerning mainly the first mentioned issue, the second one WFM in some similar way, anyway it's a pity that the solution finally couldn't apply.

[Wiktor Walc]

Does not work in Safari, the cursor is blinking below the horizontal line, but once you start typing the letters are above it.

To reproduce simply try typing after

<hr />

[Wiktor Walc]

In DIV enter mode an extra div tag is added when switching from wysiwyg to source mode, after switching few times I ended up with:

<div>
	&nbsp;</div>
<div>
	&nbsp;</div>
<div>
	&nbsp;</div>
<div>
	&nbsp;</div>
<div>
	&nbsp;</div>

[Wiktor Walc]

IE6 div enter mode:

• click with a mouse below horizontal line, start typing: text is inserted above the line

IE8 div enter mode:

• cursor is blinking at the beginning of the editing area straight after inserting the horizontal line

[Sa'ar Zac Elias]

Another failed TC (IE7):

• Create a table.
• Click bebeath it and type some text.
• Switch to source. Bogus &nbsp; is there.

[Garry Yao]

@Saar, your TC already exists in current trunk when editing empty paragraph from source thus will not be part of the patch.

[Sa'ar Zac Elias]

With enterMode = BR:

• Insert a table using the dialog.
• Click beneath.
• Type a few words and press ENTER.

Note that the caret is before the content and the enter is now above it.

[Wiktor Walc]

1. Clear all contents
2. Insert a table
3. Type "AAA", press enter 4 times (AAA was moved down)
4. Click with a mouse below the table
5. Type "BBB", press enter
6. Result: cursor is straight above "AAA", not straight below "BBB"

[Sa'ar Zac Elias]

A few more:

• When creating a table and putting the cursor beneath it, the span element is visible in the elements path.
• * Create a table with the dialog, the cursor is now beneath it.
• * Before typing any text, choose a color from color panel.
• * Type some text.
• * The text is not painted. Going to source shows redundant span.

[Sa'ar Zac Elias]

Please update the patch.

[Garry Yao]

We need a new start after [6461], as the temporary filler could benefit this situation where we can forget the padding node solution we have before.

[Sa'ar Zac Elias]

IE:

• Add a table.
• Put the caret beneath the table.
• Write one character.
• Hit BACKSPACE.

The table is unexpectedly being removed.

[Garry Yao]

Replying to Saare:

The table is unexpectedly being removed.

WFM in all IE versions, need more clues.

[Sa'ar Zac Elias]

Does not happen for me too anymore, but:
With the same steps, enterMode BR, IE8, the caret goes into the last cell instead of staying in the same line.

[Garry Yao]

Replying to Saare:

Does not happen for me too anymore, but:
With the same steps, enterMode BR, IE8, the caret goes into the last cell instead of staying in the same line.

The mission is making it possible to adding stuff at the end of document in all situation, but not to establish line-height for the last empty line or so, the issue you mentioned here is not addressable for now and being way less critical than the bug itself.

New patch fixes a bug that makes it possible to open block format once cursor is blinking at the end of doc.

[Sa'ar Zac Elias]

L109, why is a number symbol being added instead of a zero-width char?

[Garry Yao]

I've included other commonly used block that are also unable to exit from at the doc end, e.g. list, and relief the original assumption that IE<8 don't need the fix.

[Sa'ar Zac Elias]

IE8, enterMode BR, after performing the initial case described in the ticket:

• Open the format combo, choose heading 1.
• Type a letter.
• Hit CTRL+Z.

JS error occurs.

[Wiktor Walc]

We're definitely having too many problems with this ticket, so postponing.

[Anup]

This issue is reproducible on 4.5.11 as well.

[Jakub Ś]

Version is used to indicate when problem has started occurring. Don't change it.