Thursday, 27. April 2006, 11:31:01
Don't give vague error messages in JS console
I especially hatemessage: Statement on line 37: Could not convert undefined or null to object
This is absolutely unhelpful. I might have reference to 10 objects on a single line and from this message I absolutely can't figure out which one is invalid.
Firefox does it much better, simply saying "variable_name has no properties".
Thursday, 27. April 2006, 14:07:07
Another example is
vs Firefox:
Syntax error while loading: line 232 of linked script at http://...js :
vs Firefox:
Error: missing } after function body
Wednesday, 10. May 2006, 07:33:19
+1000
Opera should be user-friendly. Friendly error messages would make it easier to decode.
Opera should be user-friendly. Friendly error messages would make it easier to decode.
Saturday, 12. August 2006, 10:58:20
I don't write much javascript, but the times I do I always curse on "Could not convert undefined or null to object"- messages.
+111
+111
Monday, 14. August 2006, 19:50:57
OK, understandable error messages could be helpful.
But usually I am not the owner of the page and therefore cannot fix the error. Perhaps JavaScript and its users tend to use non-standard extensions?
To make it short: It would be better that Opera supports more page than it understandably reports errors that I cannot fix.
But usually I am not the owner of the page and therefore cannot fix the error. Perhaps JavaScript and its users tend to use non-standard extensions?
To make it short: It would be better that Opera supports more page than it understandably reports errors that I cannot fix.
Saturday, 16. September 2006, 12:53:26
+1
That's why I keep FF around. Its error console is more revealing.
That's why I keep FF around. Its error console is more revealing.
Forums » Opera Community » Opera for desktop » Desktop wish-list
