Error message for improper URLs are attributed to incorrect line

[hallpell]

In this example:

https://woofjs.com/create.html#hallpell_url-error

the error occurs in line 9 (where no URL is provided to setImageURL), but Woof reports the error on line 1. Need to process this error differently in some way.

[hallpell]

It looks like we've already tried to deal with this by scanning through the code (regex-style) to look for Empty URL Types (

WoofJS/create.html

Line 1711 in 42a2c23

if (error.url === "") {

), but we're missing some cases. Three main cases that I think are missing are:

• I don't think it ignores whitespace
• If no argument is provided (which appears as 'undefined' once it gets inside woof.js and thrown as an ImageLoadError)
• If an empty variable is provided as an argument, we're probably not going to be able to track it down regex-style, and would need to track the error from where it was thrown, which requires upgrading our architecture a bit.

I should be able to clean up the first two cases a bit fairly easily, so should be able to get that done soon.

[hallpell]

(Also setBackdropURL has an error message if a string isn't provided as the first argument, which should be added to setImageURL as well)

[hallpell]

Further investigation of this makes me not trust how we handle errors in Woof. I believe when we try to GET an image that doesn't exist, we throw two errors. The 404 error seems to not be caught properly, and is making it hard for me to properly track down how the errors are propagating.