This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://lists.w3.org/Archives/Public/public-canvas-api/2010AprJun/0013.html On Tue, 27 Apr 2010 22:46:27 +0200, Simon Pieters < simonp@opera.com> >On Tue, 27 Apr 2010 22:16:27 +0200, Jatinder Mann <jmann@microsoft.com> >wrote: >> I would like to get clarification on the following passage [1]: >> >> "In non-interactive, static, visual media, if the canvas element has >> been previously painted on (e.g. if the page was viewed in an >> interactive visual medium and is now being printed, or if some script >> that ran during the page layout process painted on the element), then >> the canvas element represents embedded content with the current image >> and size. Otherwise, the element represents its fallback content >> instead." >This seems like a stupid requirement. Why would we want to print the fallback? In many cases the fallback will be "your browser does not support canvas". Can we remove this paragraph from the spec?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: Well we have to define what the element represents, so we can't just remove it. But we can certainly change it. What should the element represent in the case of non-interactive, static, visual media?