Permission Denied to get property Window.document

[Freddie Bingham]

Occasionally, upon page load, I will receive:

Permission denied for <​http://www.example.com> to get property Window.document

This is being thrown from wysiwygarea/plugin.js:

var doc = iframe.getFrameDocument();

which is calling getFrameDocument() in element.js, which dies on

return $ && new CKEDITOR.dom.document( $.contentWindow.document );

The editor is not being called in any cross domain capacity and as I said, it happens infrequently. Frequency of the issue is increased if the "Disable Cache" option of the Firefox "Web Dev Toolbar" plugin is enabled. This option only sets preferences built into firefox so it is not at fault.

The preferences it changes are:

'browser.cache.disk.enable' 'browser.cache.memory.enable'

Tested Browser is FF 3.6.17

[Jakub Ś]

I'm not sure if I understand you correctly. You say that you place a link in CKEditor editing area and when page loads you get permission denied?

I did not get that result.

Could you provide me with more info, a simplified test case perhaps?

[Freddie Bingham]

Nothing to do with a link, doesn't matter if the editor begins with data or not. It doesn't happen very often but it does happen. The Permission denied for < ​http://www.example.com> to get property Window.document is quite a telling error. I will have to add a timeout and retry there to see if it works.

[Jakub Ś]

I have setup domain www.example.com, disabled cache in Web developer toolbar and loaded page with CKE (many, many times) but no permission denied was thrown.

Is this how you got this error and if not could you describe a step by step scenario?

Also is it possible to provide us with a sample HTML file which can help to reproduce the issue?

[Jakub Ś]

@fbingha any updates regarding this issue?

[Jakub Ś]

@fbingha any updates regarding this issue?

[Freddie Bingham]

The only update that I have is that this is happening randomly when the page is also including the facebook connect api and/or a facebook like button.

[Jakub Ś]

And could I ask you to provide reduced test case for this (file/files/sample application)?

I have tried to reproduce it few times but had no luck and you know best what is wrong and how to repeat it.

[Freddie Bingham]

You can close this bug as I have tracked down the cause to duplicate facebook elements with the same ID of "fb-root". In some odd way this caused the facebook like button iframe init to stop the the CKEditor iframe from initializing properly.