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 #9705, comment 4

Timestamp:: Dec 28, 2012, 8:09:35 PM (12 years ago)
Author:: Jakub Ś
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

TabularUnified Ticket #9705, comment 4

-                      v1
+                      v2
 . Please have a look at possible values  http://www.w3schools.com/html5/att_iframe_sandbox.asp
 . Next look at the error - "Sandbox access violation: Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL ... "Both frames are sandboxed into unique origins".
 . Taking to above into account all you have to do for **iframed editor** is (Notice allow-same-origin):
+. Next look at the error - "Sandbox access violation: Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL ... "**Both frames are sandboxed into unique origins**".
+. Taking to above into account all you have to do for **iframed editor** is (Notice **allow-same-origin**) adding extra attribute value:
 {{{
 <iframe src="replacebycode.html" width="1100" height="800" sandbox="allow-scripts allow-same-origin">