This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8804 - I see no value in making the reader go through a paragraph saying what not to do. Despite that the list is infinite, authors will do whatever they want. And ultimately if they are using certain elements for a putpose different from the original it usually
Summary: I see no value in making the reader go through a paragraph saying what not to...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-24 18:09 UTC by contributor
Modified: 2010-10-05 12:59 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-01-24 18:09:58 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-canvas-element

Comment:
I see no value in making the reader go through a paragraph saying what not to
do. Despite that the list is infinite, authors will do whatever they want. And
ultimately if they are using certain elements for a putpose different from the
original it usually is because the "right" solution provided is not that
right. I'd delete The "Authors should not use ..." paragraph in whole. 

Posted from: 190.188.9.30
Comment 1 Ian 'Hixie' Hickson 2010-02-13 12:34:23 UTC 
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: If it prevents even one author from misusing <canvas> in a way that hurts even one user, then it'll have been worth it. I see no downside here.