CKEditor support for Adobe AIR

[Frederico Caldeira Knabben]

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

#4497

Inline event handlers are ignored in AIR

iframe loading violation

#4496

All float panels are broken in AIR

[Garry Yao]

Well, we definitely have much trouble with Adobe AIR support on ​application sandbox comparing with v2, majorly because we violate many AIR HTML ​security rules in v3:

1. “javascript:” URI scheme ( Violated by wysiwyg iframe loading )
2. document.write() after page onload happened ( violated by wysiwyg iframe loading either )
3. parsing handler attributes (e.g. onclick="myFunction();") inserted with innerHTML or outerHTML ( Violated by almost every handler on UI items )

For 1 and 2, we could find workaround easily with some feature sacrifices( content doc type, content doc lang direction... ), but for 3, it will take some efforts.

Not sure if non-application-sandbox's even be a fall-back option for us?

[Garry Yao]

And it seems for me that dynamic <style> tag are also ignored.

[Garry Yao]

New ​feature branch for AIR support has been created and a plugin 'adobeair' has been committed with [4294].

[Garry Yao]

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.

[Garry Yao]

We would like to defer the support for AIR to next release, which will probably feature AIR2 which is currently under beta.

[Frederico Caldeira Knabben]

The code proposed in the adobeair branch is unacceptable. It demonstrates a strong lack of attention on details. It also introduces code formatting on some files, which makes reviewing much complicated.

[Garry Yao]

the "adobeair" branch lands on 3.5.x with [6178].