Custom Query

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (25 - 27 of 11754)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Ticket Resolution Summary Owner Reporter
#12257 fixed [Chrome] /tests/plugins/enter/list - one of tests throws error "Discontiguous selection is not supported. " Artur Delura Piotrek Koszuliński
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 Artur Delura Piotrek Koszuliński
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:

  • Implement filter.destroy() that will for safety delete the private object (this._) which keeps a lot of stuff and will remove editor from CKEDITOR.filter.instances.
  • Call editor.filter.destroy() and delete editor.filter and editor.activeFilter on editor#destroy

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 Artur Delura AlexW
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">
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Note: See TracQuery for help on using queries.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy