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 2 of Ticket #11024

Timestamp:: Oct 23, 2013, 7:28:39 AM (11 years ago)
Author:: Piotrek Koszuliński
Comment:: Perhaps we'll have to go this way. But first we want to wait, because maybe Google/Apple will fix the bug in Blink/WebKit. More details: http://dev.ckeditor.com/ticket/9929#comment:15

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11024
- Property Status changed from new to confirmed
- Property Keywords WebKit Blink added
- Property Version changed from 4.2.2 to

Ticket #11024 – Description

initial	v2
14	14	One could argue this is not a bug but normal browser behaviour, and therefore should be a feature request at best.
15	15	But since the behaviour is not what most users (content editors) will expect, i strongly think this IS a BUG.
	16
	17	Related to: #9929.