Simon Pieters wrote :
On Tue, 17 Apr 2007 22:37:16 +0200, Jordan OSETE
[EMAIL PROTECTED] wrote:
PS: is it OK to post suggestions on the message board (at
http://forums.whatwg.org/) instead of the mailing lists?
Yes.
Or maybe less people would read it?
Discussions in the forums can
Maciej Stachowiak wrote :
One reason the API works this way is that in the CoreGraphics drawing
API on
the Mac, there's no way to add anything to the clip region directly, so
it would be necessary to track all the context state manually and union
paths to support these operations. The
Jordan OSETE wrote:
Yes, but there are complex shapes that can be made really easier to draw
this way. On the other hand, the way the current specification works
allows to construct a single shape once, and draw it in different ways
around, by just modifying the transform attribute...
It
On 15/04/07, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Apr 15, 2007, at 11:15 AM, Jordan OSETE wrote:
Color / style:
--
Reading colors can be complex. Right now it returns a string either
in the form #xx or rgba(...), depending on the alpha value. It
means the reader
Hello folks at the WHATWG.
Some simple suggestions about the great canvas tag:
Clipping-paths:
---
Right now if i understand it correctly, the clip() function creates a
new clipping path, being the intersection of the last clipping path.
I have not seen any way to actually come
On Apr 15, 2007, at 11:15 AM, Jordan OSETE wrote:
Hello folks at the WHATWG.
Some simple suggestions about the great canvas tag:
Clipping-paths:
---
Right now if i understand it correctly, the clip() function creates
a new clipping path, being the intersection of the last
Maciej Stachowiak wrote:
You can achieve relative moves by doing a translation to the current
point when drawing; this is a more general version of what your pathBase
property would do.
Hi,
the WHATWG spec says you cannot do so (section 3.14.11.1.8):
Note: The transformation is applied to
