Opened 15 years ago
Closed 15 years ago
#3907 closed Bug (fixed)
CKEditor becomes non-editable in Firefox 3.5 if loaded from history cache
| Reported by: | Neil Jenkins | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.1 |
| Component: | General | Version: | |
| Keywords: | Confirmed | Cc: |
Description
Steps to reproduce:
- Open any instance of CKEditor in Firefox 3.5 (any of the demos will do).
- Press the back button on the browser.
- Press the forward button to go back to the page with the CKEditor instance.
The editor appears fully loaded but clicking inside it fails to produce a cursor - the instance is uneditable. Clicking 'Source' to view source then again to go back to wysiwyg mode reactivates it.
Verified on Firefox 3.5 on Mac OS X 10.5.7 against the release candidate and revision 3828.
Change History (5)
comment:1 Changed 15 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 Changed 15 years ago by
| Keywords: | Confirmed added |
|---|---|
| Milestone: | → CKEditor 3.1 |
| Resolution: | wontfix |
| Status: | closed → reopened |
This one is supposed to be fixed by #4514.
comment:4 Changed 15 years ago by
| Milestone: | CKEditor 3.1 → FCKeditor.Java 2.6 |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Summary: | CKEditor becomes non-editable in Firefox 3.5 if loaded from history cache → CKEditor becomes non-editable in Firefox 3.5 if loaded with text in it |
| Version: | → FCKeditor 2.6.5 |
CKEditor becomes non-editable in Firefox 3.5 if loaded with text in it
comment:5 Changed 15 years ago by
| Milestone: | FCKeditor.Java 2.6 → CKEditor 3.1 |
|---|---|
| Resolution: | → fixed |
| Status: | reopened → closed |
| Summary: | CKEditor becomes non-editable in Firefox 3.5 if loaded with text in it → CKEditor becomes non-editable in Firefox 3.5 if loaded from history cache |
| Version: | FCKeditor 2.6.5 |
This ticket has been fixed and will be available with CKEditor 3.1. If you're facing any other issue, please open a dedicated ticket to it.
Note: See
TracTickets for help on using
tickets.
The different behaviors on Back/Forward history navigation between browsers:
It seems a browser bug that the designMode is lost after loading a DOM snapshot, every other things works well for the editor, we're not likely to provide a fix at this problem.