Opened 16 years ago
Closed 16 years ago
#3160 closed Bug (fixed)
[FF] Ajax sample editor document problem
Reported by: | Garry Yao | Owned by: | Frederico Caldeira Knabben |
---|---|---|---|
Priority: | Normal | Milestone: | CKEditor 3.0 |
Component: | General | Version: | |
Keywords: | Confirmed Firefox Review+ | Cc: |
Description
Reproducing Procedures
- Open the ajax.html example page;
- Click Create Editor button to have a new instance;
- Insert some content and click Remove Editor to destroy the instance;
- Click Create Editor button again to have another new instance;
- Actual Result : The content is lost within the new instance and the document become not editable.
Attachments (2)
Change History (7)
Changed 16 years ago by
Attachment: | 3160.patch added |
---|
comment:1 Changed 16 years ago by
Keywords: | Review? added |
---|---|
Owner: | set to Garry Yao |
Status: | new → assigned |
comment:2 Changed 16 years ago by
Keywords: | Review- added; Review? removed |
---|---|
Owner: | changed from Garry Yao to Frederico Caldeira Knabben |
Status: | assigned → new |
While this patch solves the problem for this specific case, I think something more generic would be better. The fact is that, as soon as "mode" gets fired, the code should be able to interact with the mode contents without setTimeout hacks. Currently this is not doable in the "wysiwyg" mode, the browser needs time to render the document first.
I've already coded it in a new patch that's based on Garry's one. I'm taking over the ticket for it.
Changed 16 years ago by
Attachment: | 3160_2.patch added |
---|
comment:3 Changed 16 years ago by
Keywords: | Review? added; Review- removed |
---|
comment:4 Changed 16 years ago by
Keywords: | Review+ added; Review? removed |
---|---|
Version: | SVN (FCKeditor) |
Fixing the bug by avoiding cross-frame scripting security error from generated when invoke editor.setData().