[Webkit-unassigned] [Bug 80028] New: Setting crossOrigin attribute for images won't trigger onerror on CORS denial
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Mar 1 07:49:21 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=80028
Summary: Setting crossOrigin attribute for images won't trigger
onerror on CORS denial
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Windows Vista
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Images
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: niklasvh at gmail.com
Created an attachment (id=129704)
--> (https://bugs.webkit.org/attachment.cgi?id=129704&action=review)
example where onerror / onload isn't triggered
When defining the crossOrigin attribute for an Image element, it won't return an onload/onerror event if the image exists, but denied by CORS policy. In other words, there is no event to determine when the image has finished loading and whether it managed to load it, unless you check with timers for the complete attribute to change.
The expected result would be for the onerror event of the image to be triggered (as it does in Firefox), and as defined in http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html#attr-img-crossorigin "Set the img element to the broken state, and fire a simple event named error at the img element."
Tested on both 19.0.1057.0 canary and 17.0.963.56 m, and neither is triggering the real onerror in the example.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list