You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1.download rev 226
2.run index.html in google-chrome
3.
What is the expected output? What do you see instead?
Please see video
http://youtu.be/IG28hl_HeG4
What version of the product are you using? On what operating system?
r. 226
linux mint 12
Please provide any additional information below.
please see video
http://youtu.be/IG28hl_HeG4
Original issue reported on code.google.com by dennisgd...@gmail.com on 9 Jun 2012 at 8:40
The text was updated successfully, but these errors were encountered:
First, running the maze and code demos in Chrome using the local file://
protocols won't work due to a security restriction in Chrome. Firefox will run
these demos fine on file://, and Chrome will happily run the RTL demo and
test/playground.html app. However, what you describe is something else
entirely, you are getting a fatal JavaScript error even before it gets to the
point where security would shut it down.
In your case, the conflict in blockly_compressed.js is almost certainly what's
killing the system. You chose 'p' (postpone) when resolving the conflict,
meaning the conflict was not resolved and you are running the new version of
the demo with the old version of Blockly. That would certainly be a recipe for
generating a fatal error. Update again and choose 'tc' (theirs-conflict) to
update to the latest version of that file.
Original comment by neil.fra...@gmail.com on 9 Jun 2012 at 6:05
Thank you for the quick reply/response!
I Checked out revision 229.
Blockly and the goal are not on the map on Fx 13 nor on GC 19.
Please see video and screen shots.
http://youtu.be/tBLTYG5BEOE
Original comment by dennisgd...@gmail.com on 10 Jun 2012 at 11:07
Original issue reported on code.google.com by
dennisgd...@gmail.com
on 9 Jun 2012 at 8:40The text was updated successfully, but these errors were encountered: