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 14001 - 1) Please add a radiusY to the path arc command(s) so it is easier to create ellipse shapes and elliptical arcs. It would be very nice if the Canvas path supported a similar API to that for creating SVG paths via JavaScript so shapes could be exchanged
Summary: 1) Please add a radiusY to the path arc command(s) so it is easier to create...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML Canvas 2D Context (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: 2011-09-01 21:29 UTC by contributor
Modified: 2011-10-18 22:45 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-09-01 21:29:10 UTC 
Specification: http://www.w3.org/TR/2dcontext/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
1)  Please add a radiusY to the path arc command(s) so it is easier to create
ellipse shapes and elliptical arcs.  It would be very nice if the Canvas path
supported a similar API to that for creating SVG paths via JavaScript so
shapes could be exchanged between the two forms.  Perhaps even support for the
SVG Path mini-language (i.e.: "M0,0 L40,50 A... z").

2)  The "This box is non-normative..." overwrites the text below.  It's
especially troublesome when trying to print a copy for off-line reading.

3)  The document format is not well formed for printing.

4)  Will there be a PDF of this spec in the future?


Posted from: 75.57.161.136
User agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20100101 Firefox/6.0
Comment 1 Ian 'Hixie' Hickson 2011-10-18 22:45:34 UTC 
Please file only one issue per bug.

1a) I imagine we might add an ellipse feature in the future. What is your use case?
1b) There are no immediate plans to support the SVG path language, but it's something we might consider when adding path primitives.

2) Can you elaborate in a separate bug on where you see this? A screenshot would be ideal. I am not able to reproduce this.

3) Can you elaborate in a separate bug with specifics about what is problematic for printing?

4) http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032965.html


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: Please file new bugs providing the information requested above.