On Wed, Nov 25, 2009 at 12:19 AM, David Bruant
wrote:
> => I take this argument as a "pro" argument for two reasons :
> - are void elements in every single browser, so, if this "status"
> changes in HTML5, they can all change the behavior of element at
> the same time (which would be harder if s
On Nov 26, 2009, at 11:45 AM, Jason Oster wrote:
> Hello Group,
>
> I've been using canvas to draw pixel art (NES/SNES game screens and sprites)
> similar to what an emulator would do. Doing this kind of drawing requires
> direct access to the pixel buffer.
>
> My problem with the canvas spe
Hi, I made a forumpost : http://forums.whatwg.org/viewtopic.php?t=4176,
concerning a possible "microdata specification bug" and a bug in the
james.html5.org microdata extractor.
Comes down to and elements possibly being unfit for use
with the itemscope attribute.
I made an example in the f
Hello Group,
I've been using canvas to draw pixel art (NES/SNES game screens and sprites)
similar to what an emulator would do. Doing this kind of drawing requires
direct access to the pixel buffer.
My problem with the canvas spec (as it is now) is that it tends to artificially
bounds pixel d
In the section for the time element, the spec states:
"This element is intended as a way to encode modern dates and times in
a machine-readable way so that user agents can offer to add them to
the user's calendar."
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-seman
> For what it's worth, I believe that the option (1) choice of
> minimumCapacity in my original email would be quite easy to implement on
> WebKit for iPhone and Safari UAs: just return 5MB.
On Thu, Nov 26, 2009 at 3:18 AM, Ian Hickson wrote:
> The iPhone has GBs of storage, though, so it's proba
There's ErrorEvent.initErrorEvent, and dispatchEvent is exposed in
workers, but there's no createEvent (because there's no document). Are
there use cases for sending events in a worker? Should we expose
createEvent somewhere? Should we remove initErrorEvent?
--
Simon Pieters
Opera Software