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 4 of Ticket #11111

Timestamp:: Sep 5, 2014, 1:29:36 PM (10 years ago)
Author:: Piotrek Koszuliński
Comment:: The same regression made up to Chrome - #12221.

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11111
- Property Status changed from new to confirmed
- Property Summary changed from [Safari] Range.enlarge test failing in Safari 7.0 to [Safari] Range.enlarge test failing in Safari 7.0 and Chrome 37

Ticket #11111 – Description

-                      initial
+                      v4
 Test /dt/core/dom/range/enlarge.html#test_enlarge_element12 fails in latest Safari 7.0 that comes with OSX 10.9.
+Test /dt/core/dom/range/enlarge.html#test_enlarge_element12 fails in latest Safari 7.0 that comes with OSX 10.9. It's also reproducible in Chrome 37 (see #12221).
 The root of the problem is the following condition: https://github.com/ckeditor/ckeditor-dev/blob/major/core/dom/range.js#L1039
 …
 That particular test fails since CKeditor 4.0 in Safari 7 which makes it clear that we're facing Safari regression.
+Related bug in Chrome: #12221.