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

Changes between Version 2 and Version 3 of Ticket #16768

Timestamp:: Jan 2, 2017, 11:28:29 AM (7 years ago)
Author:: Marek Lewandowski
Comment:: This is well known inconsistency between the browsers, but I can't find the ticket number. Pinged @j.swiderski for help.

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #16768 – Description

v2	v3
88	88	----
89	89
90		While the elements order may be different I does not make any difference for visual appearance and CKEditor UI (`<a><em>text^</em></a>` and `<em><a>text^</a></em>` looks same and activates same states/controls in UI). This means for different elements order, the result of using styles combo should be the same ~~in both appearance and UI state (same for one browser, not necessarily between browsers~~).
	90	While the elements order may be different I does not make any difference for visual appearance and CKEditor UI (`<a><em>text^</em></a>` and `<em><a>text^</a></em>` looks same and activates same states/controls in UI). This means for different elements order, the result of using styles combo should be the same (in both appearance and UI state).