If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Expose API for getting path of text to canvas

NEW
Unassigned

Status

()

Core
Canvas: 2D
7 years ago
3 years ago

People

(Reporter: jrmuizel, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [shumway])

(Reporter)

Description

7 years ago
It would be useful for authors to be able to obtain the path associated with text. This probably means exposing some sort of path object.

Updated

6 years ago
QA Contact: canvas.2d → jmuizelaar
(Reporter)

Comment 1

6 years ago
There's no point in rushing to add this API until we have good reason to. I'd at least wait until the old canvas backend is gone.
Summary: Expose text path from canvas → Expose API for getting path of text to canvas
(Reporter)

Updated

6 years ago
QA Contact: jmuizelaar → canvas.2d
Canvas v5 added support for Path primitives (http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#path-objects) and there is addText and addPathByStrokingText on Path objects.
Blocks: 927828
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [shumway]
From the bug description, this is not what addText is doing. addText is drawing a text along a path, this bug is about an API to get the path associated with text.
Blocks: 1038057
Tobias says this is not a Shumway blocker. Assigning to Tobias as a point of contact.
No longer blocks: 927828
You need to log in before you can comment on or make changes to this bug.