-
-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dojo/parser::parse() error #318
Comments
this is the only real difference in the setup of HtmlUnit from real browsers - because it was developed as testing tool webClient.getOptions().setThrowExceptionOnScriptError(false); |
I fixed the javascript error and will close this. Thanks |
Actually, I am still getting the same error (I thought it was something else). The Bar.js error is gone, but still stopping in htmlunit. Feb 25, 2021 9:50:56 AM com.gargoylesoftware.htmlunit.WebConsole error SEVERE: dojo/parser::parse() error InternalError: Could not convert JavaScript argument arg 0 (http://localhost:9080/Navigator/scripts.f1f53a09317b5a0c80d3.js#1) |
How can I get a stack trace or more information on this error coming out of HtmlUnit? I know it is complaining about the dojo parse and Angular generated file script js, but don't enough to go on. |
Tricky. http://localhost:9080/Navigator/scripts.f1f53a09317b5a0c80d3.js#1 - the 1 point to line source code line number - usually this is a minified and maybe obfuscated version of the js source. It will be a great help to change the app in a way to use the plain source (DEV mode). Then you are able to determine the problematic line and with a bit of luck you can see why the receiver of watch is undefined. Maybe there is a property not implemented in HtmlUnit or something like this..... |
I have fully decompressed the js source but get the same error.
to get dev mode:
attached is the script source within the Navigator server being run |
But i hope the line number is changed - what is the new number when running the decompressed source? |
I am still getting the same line number (#1)... |
When launching to my chart (this is in new project location using Angular2 & dojo with Maven build process where I haven't gotten to that point yet), I am ending with an error that it looks like HtmlUnit is passing on from dojo/parser.
Interesting thing is that I didn't think I was getting this error when running through the browser, but I do see something that could be the same when I go to console and see an error:
So ideally we will fix this error and not have any problems. But it is interesting that when running on browser, we hit the error but keep on. In HtmlUnit, this is where things come to a halt. Any way we can get more info on why HtmlUnit abandons it?
The text was updated successfully, but these errors were encountered: