Summary: | HTMLImageElement's "complete" attribute should be false for empty images | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Andreas Kling <kling> | ||||
Component: | Images | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED INVALID | ||||||
Severity: | Normal | CC: | ap, darin, ian | ||||
Priority: | P2 | Keywords: | HTML5 | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Andreas Kling
2010-07-08 13:41:16 PDT
Created attachment 60951 [details]
Proposed patch
Comment on attachment 60951 [details]
Proposed patch
I just tried this in Firefox:
javascript:(new Image()).complete
And I got the value "true". It's great to match the HTML5 specification, but I worry that we are moving from matching Firefox to not matching it. Can we discuss this on the WHATWG mailing list before making the change?
(In reply to comment #2) > It's great to match the HTML5 specification, but I worry that we are moving from matching Firefox to not matching it. Can we discuss this on the WHATWG mailing list before making the change? Indeed, we would be the first to implement this behavior. I'll post something to [whatwg] in a sec. Posted on the WHATWG mailing list: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027086.html Comment on attachment 60951 [details]
Proposed patch
Looks like no one has replied to your message yet. This patch appears to be blocked on feedback from the working group. Please feel free to re-nominate for review when we're sure we want to do this.
Is there more motivation for making this change beyond just the spec?
(In reply to comment #5) > Is there more motivation for making this change beyond just the spec? No, that's pretty much it. Though I personally like that it makes it easy to create an image with complete=false for testing purposes. Note: the spec has changed. (In reply to comment #7) > Note: the spec has changed. Thanks for letting us know. I’ll close this. |