Opened 14 years ago
Closed 12 years ago
#7821 closed Bug (fixed)
IE: unable to type above the table
Reported by: | Wiktor Walc | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | CKEditor 4.0 |
Component: | General | Version: | 3.5.4 |
Keywords: | Cc: | satya_minnekanti@… |
Description
To reproduce the defect:
- Open Ajax sample, with out focus in Editor body click on Table icon.
- Click OK button on Table Properties dialog to insert the table.
- Table is inserted & cursor in last table cell.
- Using mouse or keyboard try to keep the cursor above the Table.
Issue:
In CKEditor 3.5.3 a paragraph was created automatically after clicking above the table. Currently nothing happens and there is no easy way to add content above the table.
Tested against IE6
Regression since [6698].
Change History (9)
comment:1 Changed 14 years ago by
Status: | new → confirmed |
---|
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
As discussed before, there could be various ways (e.g. keystroke override, helper tool) of bringing the fix (establish the paragraph) while they must all obey the rule that it should only happen upon user's intention, which means we must not make any change until it's sure that user really want to edit before the table.
comment:4 Changed 14 years ago by
Cc: | satya_minnekanti@… added |
---|
comment:5 Changed 14 years ago by
Milestone: | CKEditor 3.5.4 |
---|
comment:9 Changed 12 years ago by
Milestone: | → CKEditor 4.0 |
---|---|
Resolution: | → fixed |
Status: | confirmed → closed |
Yes, the magicline plugin came to solve problems like this.
It was introduced by purpose when I was working on #6629, it doesn't looks like a good manner for breaking ticket relevance, but the reason is that, this feature (automatically add empty paragraph before table if selection is inside body), even considered useful at times, is quite counter-intuitive and obtrusive, and been unable to revert makes it even worse, so we have tickets like #5378, #6217 and #7289, we have also complaints at forum.
I guess we'd leave it as is, leave a changelog in release to explain users, and look for a better way of introducing it in the future.