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 10126 - The arc() function's last argument should be optional. Webkit doesn't require it, treating it as false if not provided.
Summary: The arc() function's last argument should be optional. Webkit doesn't requir...
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: ---
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-07-10 05:39 UTC by contributor
Modified: 2010-10-05 12:58 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-10 05:39:57 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#complex-shapes-(paths)

Comment:
The arc() function's last argument should be optional.	Webkit doesn't require
it, treating it as false if not provided.

Posted from: 76.253.3.102
Comment 1 Ian 'Hixie' Hickson 2010-08-30 18:42:08 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: Why would it be optional? You need to know what direction to go in; why does clockwise make so much more sense that we should just assume it?
Comment 2 Tab Atkins Jr. 2010-08-30 19:55:07 UTC 
(In reply to comment #1)
> Rationale: Why would it be optional? You need to know what direction to go in;
> why does clockwise make so much more sense that we should just assume it?

Assuming one direction or another is helpful to authors in the first place; why force them to make an explicit choice when clockwise is a perfectly adequate default?

More generally, whenever I see a trailing boolean argument, I assume that I can leave it out and it will just be filled by undefined, equivalent to false.  Putting in a ",false" at the end of all my functions is opaque and annoying.