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 1 and Version 2 of Ticket #9814, comment 12

Timestamp:: May 8, 2014, 9:32:14 AM (10 years ago)
Author:: Bram
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9814, comment 12

v1	v2
1	1	Replying to [comment:11 Reinmar]:
2	2	> Editor starts in read only mode and that mode is not refreshed (because how could it be) when container's visibility is changed.
3		Having to watch the visibility of each element would indeed be a hassle (is ~~this is~~ even possible without polling?). As far as I know the only way to make the editor's control bar to appear is when you focus the content-editable element.
	3	Having to watch the visibility of each element would indeed be a hassle (is it even possible without polling?). As far as I know the only way to make the editor's control bar to appear is when you focus the content-editable element.
4	4	If this is the case, the focus event could be used to refresh the '''isReadOnly''' check and render the control bar correctly based on the element's current visibility.
5	5