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 #4090

Timestamp:: Dec 1, 2009, 1:55:49 PM (15 years ago)
Author:: Garry Yao
Comment:: Though at this moment we've almost code complete with this feature, while there's not much time left for us to properly testing everything to guarantee the quality, we've decided to ship it with next release.

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #4090
- Property Keywords Umbrella added
- Property Owner set to Garry Yao
- Property Status changed from new to assigned
- Property Milestone changed from CKEditor 3.1 to CKEditor 3.2

Ticket #4090 – Description

-                      initial
+                      v4
+CKEditor should run properly inside an AIR application.
+CKEditor should run properly on Adobe AIR in '''application sandbox'''. This is an umbrella ticket, it points to several tickets which mostly targeting workaround for editor's original design goals which violate AIR's security rules.
+=== inline event handler violation ===
+[[TicketQuery(id=4497)]]
+=== iframe loading violation ===
+[[TicketQuery(id=4496)]]