- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Sep 2012 07:40:10 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18787 Summary: Canvas fallback is not activated on script failure Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML5 spec AssignedTo: erika.doyle@microsoft.com ReportedBy: peter.winnberg@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org When the script that is responsible for drawing something onto a canvas element fails to load (unable to download the file or syntax error) the fallback for that canvas element is not activated. The specification only seems to cover how fallback content should be handled when scripting is completely disabled and when the canvas element is unsupported. That the fallback content on the canvas element isn’t activated when the script cannot be downloaded is also inconsistent with how fallback content is handled on the img element. If the image associated with the img element cannot be downloaded, the fallback is activated. Is there a need to have an more explicit relationship between the drawing method and the canvas element so failures like this can be detected? -- 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, 6 September 2012 07:40:16 UTC