anybody come upon this bug? Ben?
June 1, 2012 12:00 AM
Hi guys,
Sent Lectora support an email with a bug discovered today. Wonder if anybody else has discovered it? In brief, variables do not work in Google Chrome 19.0.1084.52 being run on Windows 7 home premium when the html is run locally (not on a webserver).
Anyone? I would just be surprised if I was the first to discover it.
I mocked up a very simple example to demonstrate issue. Source files tiny at 32kb. I'll give the full explanation here.
Explanation
In brief, variables do not work in Google Chrome 19.0.1084.52 being run on Windows 7 home premium if html is run locally and not on a webserver. I'm using lectora vx.6 (8458).
To demonstrate, run this link (Page 1 below) with the above requirements above.
Page 1
You will see it works fine. HOWEVER, now put the html locally on your computer and run again under the same conditions and u will see that the variable values are lost. I wud be surprised if such a basic bug had not already been reported.
So to run the html locally, u can get my source from....
http://www.rasheff.com/chromebug.zip
(it is only 32kb)
The html is published out, but please do publish it out again if u like. Now place your html folder locally on your C drive or D drive or wherever (not on a webserver) and run the page again. You'll see when you click the "Click 3" button that variables do not work in Google Chrome 19.0.1084.52 when the html is just local (not on any webserver).
To solve the bug u can just run the html on any webserver and it is fine. But, obviously the bug I am reporting is serious and fundamental to anybody running an html course with Chrome and locally.
Discussions have been disabled for this post