This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/edits.html Multipage: http://www.whatwg.org/C#update-the-image-data Complete: http://www.whatwg.org/c#update-the-image-data Referrer: Comment: <img> URL that fails to resolve should fire 'error' event etc http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3058 (That url fails to resolve in gecko and blink at least, per http://krijnhoetmer.nl/irc-logs/whatwg/20140612#l-320 ) Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 OPR/22.0.1471.40 (Edition Next)
http://w3c-test.org/submissions/996/html/semantics/embedded-content/the-img-element/update-the-image-data/markup-with-src-content-unresolvable-url.html IE and Gecko don't fire any events here (like the spec). Blink and WebKit fire error. http://w3c-test.org/submissions/996/html/semantics/embedded-content/the-img-element/update-the-image-data/set-src-content-unresolvable-url.html http://w3c-test.org/submissions/996/html/semantics/embedded-content/the-img-element/update-the-image-data/set-src-idl-unresolvable-url.html IE throws an exception. Gecko and Chrome 35 fires error event and sync sets .complete to true. Chrome canary fires error and async sets .complete to true.
I prefer the Chrome canary behavior since it's most similar to what happens when the image fails to load.
Fire error event when URL fails to parse. https://github.com/ResponsiveImagesCG/picture-element/commit/22efd4478d7714ac12fd128ca2c455d0f91f42a4