- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 30 Mar 2010 02:52:49 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9190 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-03-30 02:52:49 --- 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: Rejected Change Description: no spec change Rationale: I don't think that would make sense given the way canvas generally is expected to be used. In fact, I can't really think of any case where you would want that. If you have any concrete examples where each time fillText() is called, text is placed somewhere in the fallback, please let me know. I'd love to study the design patterns that lead to such a scenario; it might provide insight into other things we could do too. In the absence of such an example, though, I haven't changed the spec. -- Configure bugmail: http://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 Tuesday, 30 March 2010 02:52:52 UTC