search

jak786 / blockly

Automatically exported from code.google.com/p/blockly
0 stars 0 forks source link

Fails in chromium when accessed via file:// #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Check out the code
2. Fire up chromium
3. Navigate to the maze demo via file://

You get a popup with the text:

    Error: Unable to communicate between frames.

    This may be due to a security restriction preventing
    access when using the file:// protocol.

I think this is probably yet another instance of

http://code.google.com/p/chromium/issues/detail?id=47416

but with a dash of irony to spice it up.

Original issue reported on code.google.com by Mar...@reality.com on 14 Jun 2012 at 12:52

GoogleCodeExporter commented 9 years ago 
Correct on all counts.

As it says on that bug (comment 14):
"If you want to show interest in having this behavior changed please star the 
issue."

I've stared the issue (please do so too).  I've also inserted a link to that 
issue in Blockly's error alert when it detects an inter-frame communication 
failure in file:// mode.  It will land in the next Subversion commit.

Thanks for the link.  I don't think there's anything more we can do at this end.

Note that this only affects Blockly when nested in an iframe.  The developer's 
test page 'tests/playground.html' is not nested in an iframe, specifically for 
this reason.

Original comment by neil.fra...@gmail.com on 14 Jun 2012 at 1:13