Ticket #3032 (closed Bug: fixed)
Event 'instanceReady' doesn't work in certain case
| Reported by: | garry.yao | Owned by: | garry.yao |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | 3.0 Beta 2 |
| Keywords: | Cc: |
Description
Specifically, the instanceReady was triggered twice when edito r created in 'append' mode and the editor isn't fully interacted in because of incorrect state of 'dirty' flag.
Attachments
Change History
Changed 4 years ago by garry.yao
- Attachment test-editor-instanceReady.patch added
comment:2 Changed 4 years ago by garry.yao
- Owner set to garry.yao
- Status changed from new to assigned
comment:4 Changed 4 years ago by fredck
- Keywords Review- WorksForMe added; Review? removed
I can't understand this issue fully. The ticket points to "instanceReady" being fired twice, and the test case is checking for the dirty state.
I've changed the replacebycode sample, making the following for the first instance:
CKEDITOR.replace( 'editor1',
{
on :
{
instanceReady : function( ev )
{
document.title += ' (' + ev.editor.name + ')';
}
}
} );
Everything works properly, and the event is always fired, once only.
Maybe this has been fixed by recent changes. Can you confirm it, giving a real example other than the test case?
comment:5 Changed 4 years ago by garry.yao
The description is misleading and out-of-date, the problem handled by this ticket is only about:
Event listener for "instanceReady" doesn't grab a correct 'dirtyFlag' value, as the TC described, Since this is a internal error, it's hard to reproduce at UI level.
comment:6 Changed 4 years ago by fredck
- Priority changed from High to Normal
- Keywords WorksForMe removed
comment:8 Changed 4 years ago by alfonsoml
- Version changed from SVN (FCKeditor) to CKEditor 3.0 Beta 2
comment:9 Changed 3 years ago by fredck
- Milestone CKEditor 3.x deleted
Milestone CKEditor 3.x deleted
comment:10 Changed 7 weeks ago by Reinmar
- Status changed from review_failed to closed
- Resolution set to fixed
Expired. TC we currently have points to #9872.
Functional test case.