Tade0

It seems that it's pretty easy to have that additional code that's in http://sdk.ckeditor.dev/offline/samples/api.html, but it still has some artifacts(mostly additional whitespace inside of textareas). I'm currently in the process...

Update: I figured that instead of using variables that normally serve some arcane purpose I'll simply use the present, generated HTML output for the external code editors. Works a lot...

Summary of this ticket(based on https://github.com/ckeditor/ckeditor-sdk/pull/180#issuecomment-222621527): 1. I tried a few approaches, and a clean solution doesn't seem to exist. I guess it would be good to notify the users...

That JSFiddle problem may have something to do with the fact, that the external resources are loaded with `http://...` instead of `https://...`. I'll change the protocol and we'll see if...

1. Added title and alt. 2. I figured that since it's explicitly stated in the comment within sample: `Configure your file manager integration` the user is going understand, that this...

I went through _all_ of the samples and this is their status: - http://sdk.ckeditor.com/samples/styles.html - even after correcting the CSS paths the sample doesn't work like it should. After clicking...

I couldn't agree more. Added an appropriate commit to the PR.

I've implemented a proposed solution: 3dbdef0aeefe995b62d7d0f9234f313bd71e36db. Tests are green, manual passes, also the built version works(the `plugin.js` file is also significantly smaller). Is a manual test in order here?

Turns out this solution didn't work for the start. Fixed it and re-written the tests.

A curious thing occurred to me: the listeners that I've been manipulating seem not to be the ones that actually do the job. Investigating now what's happening here.