- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Aug 2012 10:06:08 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18742 Summary: tests relying on HTMLImageElement.complete are incorrect Product: HTML WG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: testsuite AssignedTo: dave.null@w3.org ReportedBy: jussi.kukkonen@intel.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org Spec says: --- The IDL attribute complete must return true if any of the following conditions is true: The src attribute is omitted. The src attribute's value is the empty string. The final task that is queued by the networking task source once the resource has been fetched has been queued, but has not yet been run, and the img element is not in the broken state. The img element is completely available. Otherwise, the attribute must return false. The value of complete can thus change while a script is executing. --- Still, the tests that use img.complete seem to rely on it having the "final" value instantly when the script execution starts. E.g. 2d.pattern.image.broken: var img = document.getElementById('broken.png'); _assertSame(img.complete, false, "img.complete", "false"); In reality the image decoder may, or may not, still be working on the image at that point... I don't have great ideas on how to fix this: A timeout does the job but in the end it's just as flaky as the current code. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 30 August 2012 10:06:18 UTC