Changes between Initial Version and Version 1 of Ticket #13122
- Timestamp:
- Mar 31, 2015, 9:39:29 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13122
-
Property
Status
changed from
newtoconfirmed
-
Property
Status
changed from
-
Ticket #13122 – Description
initial v1 2 2 2. `CKEDITOR.instances.editor1.document.on( 'click', function() { console.log( 'click1' ) } );` 3 3 3. Test that it works. OK. 4 4. CKEDITOR.instances.editor1.setData( 'xxx' );4 4. `CKEDITOR.instances.editor1.setData( 'xxx' );` 5 5 5. Test that the click listener no longer works. OK. 6 6 6. `CKEDITOR.instances.editor1.document.on( 'click', function() { console.log( 'click2' ) } );` 7 7 7. Test that it works. **NOK**. 8 8 9 In general - if listener to some event was attached before set data, then it will no longer work after setting data and it won't be possible to attach a new one.9 In general - if listener to some event was attached before set data, then it will no longer work after setting data and it won't be possible to attach a new listener to that event. 10 10 11 11 The reason is that setting data (unlike switching modes) keeps **the same document**, but writing to that document removes all its previous listeners. 12 12 13 On every `domObject.on()` we push the listener to `domObject.getCustomData( '_' )` listeners repository and if a native listener has not been added yet we add it to the native element.13 On every `domObject.on()` we push the listener to `domObject.getCustomData( '_' )` (the listeners repository) and if a native listener has not been added yet we add it to the native element. So there's only one native listener per event name. 14 14 15 15 Since setting data keeps the same document, the custom data (our listeners repository) stays the same. But the native listeners are removed. This means that when trying to add a new listener editor thinks that a native listener was already added, because the listeners repository already contains an entry for that event.
