On Fri, Jun 24, 2011 at 10:52 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
That's true if you call fillRect(), or fill() on a path that you've emitted
while the current matrix is singular; the rectangle or path collapses to a
single point (or line). I think it's completely clear browsers
On 6/26/11 6:14 PM, Aryeh Gregor wrote:
So this is probably my pure math background showing through rather
than a very useful contribution to the discussion. If the API were
designed for mathematicians, now . . .
The argument could still be made that we want behavior to be continuous
Gradients already aren't continuous where the start and end points are
equal. I think it would be OK to draw nothing as Aryeh suggests. At least
it's easy to spec and implement, and I doubt authors will care (they haven't
cared about the browser behaviors so far AFAIK).
On 6/26/11 8:18 PM, Robert O'Callahan wrote:
Gradients already aren't continuous where the start and end points are
equal. I think it would be OK to draw nothing as Aryeh suggests. At
least it's easy to spec and implement, and I doubt authors will care
(they haven't cared about the browser
On Mon, Jun 27, 2011 at 2:11 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/26/11 8:18 PM, Robert O'Callahan wrote:
Gradients already aren't continuous where the start and end points are
equal. I think it would be OK to draw nothing as Aryeh suggests. At
least it's easy to spec and
Hi,
my name is Rob Manson and I'm one of the co-founders of
http://ARStandards.org and an Invited Expert on the W3C Points of
Interest Working Group http://www.w3.org/2010/POI/
I've recently published an outline for a web standards based model for
AR that is obviously closely related to all the
In the user feedback from the schema.org proposal, which uses microdata as
its syntax, we have seen several use cases that would seem to require
multiple itemtypes per itemscope.
Currently the microdata spec only allows one itemtype which defines the
meaning of the vocabulary for subsequent
