Custom Query
Results (25 - 27 of 11754)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#12257 | fixed | [Chrome] /tests/plugins/enter/list - one of tests throws error "Discontiguous selection is not supported. " | ||
Description |
Run: http://tests.ckeditor.dev:1030/tests/plugins/enter/list One of tests throw: Discontiguous selection is not supported. selection.js:1974 CKEDITOR.dom.selection.selectRanges selection.js:1974 CKEDITOR.dom.range.select selection.js:1014 CKEDITOR.plugins.enterkey.enterBlock plugin.js:392 enter plugin.js:525 editor.addCommand.exec plugin.js:13 exec command.js:52 CKEDITOR.tools.extend.execCommand editor.js:825 assertEnter list:92 Tests pass, but we're apparently trying to do something incorrect. |
|||
#12261 | fixed | Filter has to be destroyed and removed from CKEDITOR.filter.instances on editor destroy | ||
Description |
This issue is related to #11010 (it's a sub case of it). When filter is created it's registered in CKEDITOR.filter.instances. Unfortunately, we haven't got time to implement any mechanism cleaning this on editor destroy. Therefore, when system destroys and initialises editors many time, the pile of filters grows and each filter consumes pretty a lot of memory. The solution should be simple. From my tests it seems that this will be enough:
We can also track some other big objects that are retained after editor destroy and try deleting references we know off. Sometimes it won't help, but some times it may. Based on http://ckeditor.com/forums/CKEditor/CKEditor-multiple-instance-memory-leak |
|||
#12279 | fixed | Allow passing custom evaluator to node.getAscendant | ||
Description |
getAscendant is a bit limited, would be handy if it could filter by classes too. // <div class="outer"><div class="inner"><p><b>Some text</b></p></div></div> // If node == <b> ascendant = node.getAscendant('div.outer'); // ascendant == <div class="outer"> |