pvdung / ourlibrary

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

ReferenceError: Can't find variable: restoreElement (line #5626) #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. go to builder page select everything except stuff in "Combinations" and 
"Options" areas
2. click build
3. include the downloaded mylib.js in a page

What is the expected output? What do you see instead?
I expect no errors to be generated. Instead I see an error.

Safari: "ReferenceError: Can't find variable: restoreElement"
Firefox: "restoreElement is not defined"

What version of the product are you using? On what operating system?
Sun, 28 Mar 2010 22:09:11 UTC

Please provide any additional information below.
attached is a minimal test case.

Original issue reported on code.google.com by johnm...@gmail.com on 28 Mar 2010 at 10:22

Attachments:

GoogleCodeExporter commented 9 years ago
I should add that if the XHTML stuff is not filtered out the error does not 
appear.

Original comment by johnm...@gmail.com on 28 Mar 2010 at 10:26

GoogleCodeExporter commented 9 years ago
Oops, I meant if everything is selected the errors goes away. Here's to error 
report comment spam :)

Original comment by johnm...@gmail.com on 28 Mar 2010 at 10:32

GoogleCodeExporter commented 9 years ago
Yeah, that was a mistake introduced recently.  One line was out of the block it 
was 
supposed to be in.  It was unrelated to the new XHTML filter option.  Thanks 
for 
spotting that!

Original comment by dmark.ci...@gmail.com on 28 Mar 2010 at 10:47

GoogleCodeExporter commented 9 years ago
Also should mention that using the Test Page prior to downloading a partial 
build 
can save you some time.  There are so many combinations possible that I really 
need 
a robot to test all of them.  :)

If the server side script doesn't do its job with regard to dependencies (as 
has 
happened before), the result is an exception on loading the Test Page.  In this 
case 
it was a fault in the client side script that didn't show up when using the 
full 
build.

Thanks again for spotting the problem!

Original comment by dmark.ci...@gmail.com on 28 Mar 2010 at 11:25