We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket History
Next Change →

Changes between Initial Version and Version 1 of Ticket #3841

Timestamp:: Jun 26, 2009, 9:20:35 AM (15 years ago)
Author:: Garry Yao
Comment:: Tight up the description.

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #3841 – Description

-                      initial
+                      v1
 ===The Problem===
+=== The Problem ===
 The current filter system doesn't respect filter rule '''priority''':[[BR]]
   When rule A is specified with priority higher than rule B when adding to filter system, what expected is all rules items of A will be applied before rules from B.[[BR]]
+When rule A is specified with priority higher than rule B when adding to filter system, what expected is all rules items of A will be applied before rules from B.[[BR]]
 Unfortunatelly, the current system doesn't allow this happen: the current behavior is different, in which it only guarantee the priority of the same rule item, so one rule imposed on the parent node could never come later than it's child's rule.[[BR]]
 If now we have