<img style="" src="" onerror='this.style.visibility = "hidden"' />

This very simple onerror event handler hides the image if it can't be found.

It works as intended in Chrome, but in Firefox, it does nothing.

Here is a jsFiddle you can try running in Chrome and Firefox to see it in action.

/

Why does firefox not work?

Any help would be appreciated

<img style="" src="" onerror='this.style.visibility = "hidden"' />

This very simple onerror event handler hides the image if it can't be found.

It works as intended in Chrome, but in Firefox, it does nothing.

Here is a jsFiddle you can try running in Chrome and Firefox to see it in action.

http://jsfiddle/y9e88ack/

Why does firefox not work?

Any help would be appreciated

• javascript
• html
• firefox

• 1 It works fine in FireFox if you actually give it a src attribute that doesn't point to an image (not empty string). Any reason why you're using an empty attribute, using inline events, or why you're expecting an error to occur? – Ian Commented Oct 29, 2014 at 1:26
• 1 @Ian Welp, want to write that up as an answer? – Nikita240 Commented Oct 29, 2014 at 1:28

1 Answer 1

I'm not sure of the internal reasoning between browsers, but Firefox will gladly fire the onerror callback when an invalid, non-empty attribute is provided. For example:

<img style="" src="asdf.jpg" onerror='this.style.visibility = "hidden"' />

DEMO: http://jsfiddle/18ga9hh8/

In both browsers, when there's an empty src attribute, there is no request made to the server (watched with Developer Tools' network tab).

When an invalid, non-empty src is provided, a request is made and both receive a 404 response, triggering the onerror callback (expected).

As you've pointed out, using a value of "?" forces your desired behavior on both browsers. What it does is make a request (can be the current page's URL, or the current page's directory, because it is considered a relative path - depends on what the browser is designed to do) but fails to apply it as an image (it's an HTML response), causing the error.

If you're wondering or care, the HTML5 spec says this about the src attribute:

The src attribute must be present, and must contain a valid non-empty URL potentially surrounded by spaces referencing a non-interactive, optionally animated, image resource that is neither paged nor scripted.

And if you look a little further down the page to the list for When the user agent is to update the image data of an img element, it must run the following steps, #10 says the following:

If selected source is null, then set the element to the broken state, queue a task to fire a simple event named error at the img element, and abort these steps.

So it looks like Firefox isn't adhering to the spec, but maybe I'm interpreting it wrong?

Using the W3C validator, an empty src attribute causes a validation error, while using a value of "?" is valid (remember the whole relative path thing?). Note that adding a querystring (what the ? should be doing) is supposed to cause the browser to never cache the image, so I don't think caching of actual images can be achieved using this approach, if desired.