http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#mime-types
There was some discussion about this, last in
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-May/026409.html
I've tested Firefox 3.6.4, Firefox 4.0b1 and Chrome 5.0.375.99 and none
return maybe for
2010/7/15 Adam Barth w...@adambarth.com:
Personally, I think we should stop screwing with postMessage and let
it be a stable enough API that folks can rely upon it.
Screwing with the spec, or with implementations? The spec, as currently
written, is not compatible with the majority of
On Mon, Jul 19, 2010 at 11:20 PM, Philip Jägenstedt phil...@opera.comwrote:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#mime-types
There was some discussion about this, last in
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-May/026409.html
I've tested
On Mon, 19 Jul 2010 14:56:09 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
On Mon, Jul 19, 2010 at 11:20 PM, Philip Jägenstedt
phil...@opera.comwrote:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#mime-types
There was some discussion about this, last in
On 19.07.2010 14:56, Robert O'Callahan wrote:
On Mon, Jul 19, 2010 at 11:20 PM, Philip Jägenstedt phil...@opera.com
mailto:phil...@opera.com wrote:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#mime-types
There was some discussion about this, last in
Canvas would benefit from a way to set stroke alignment. With the only
available alignment being center, which is not very useful, custom paths
have to be drawn to mimic inside and outside stroke alignment. That
workaround may give unwanted transparency on pixels between a path and
its stroke
On 7/19/10 8:56 AM, Hallvord R M Steen wrote:
I have no idea when other implementations of postMessage() were
written. However, throw an exception if targetOrigin has a
path/query/fragment is a spec requirement since October 2008
according to this change:
Wow, that would be so enormously useful. You make a shape, add a shape inside
of it that is 100x100, add a stroke, get the width and it's 101. This error
cascades, and shifts your items around on redraw. The math workaround is not
easy.
FWIW, Photoshop uses position for this option (I don't
On Mon, Jul 19, 2010 at 5:56 AM, Hallvord R M Steen hallv...@gmail.com wrote:
2010/7/15 Adam Barth w...@adambarth.com:
So, I'd prefer
that we didn't change APIs after shipping them unless necessary. If
we keep changing shipping APIs, we'll exhaust early adopters, which is
bad for the
The spec describes the transform() method as follows:
The transform(m11, m12, m21, m22, dx, dy) method must multiply the current
transformation matrix with the matrix described by:
m11 m21 dx
m12 m22 dy
0 0 1
The first number in these argument names is the column
While I'm harping on the transform() method, I'd like to point out that
the current spec text must multiply the current transformation matrix
with the matrix described by... is ambiguous because matrix
multiplication is not commutative. Perhaps an explicit formula that
showed the order would
On Mon, Jul 19, 2010 at 3:54 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/19/10 4:13 PM, David Flanagan wrote:
The spec describes the transform() method as follows:
The transform(m11, m12, m21, m22, dx, dy) method must multiply the
current transformation matrix with the matrix described
Greetings!
The current draft of HTML5 [1] says about rendering radial gradients:
This effectively creates a cone, touched by the two circles defined in
the creation of the gradient, with the part of the cone before the start
circle (0.0) using the color of the first offset, the part of the
13 matches
Mail list logo
