Le 11 avr. 2007 à 17:21, Maciej Stachowiak a écrit :
"The img element represents a piece of text with an alternate
graphical representation."
And also:
"When the alt attribute's value is the empty string, the image
supplements the surrounding content. In such cases, the image could
be om
At
http://bewest.wordpress.com/2007/04/10/webforms-2-submissionvalidation-model/
, I discuss the submission/validation algorithm specified in
http://www.whatwg.org/specs/web-forms/current-work/#form-submission .
Applications won't be able to trust any incoming input, without some mechanism
that en
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
On Apr 14, 2007, at 10:01 PM, gary turner wrote:
Maciej Stachowiak wrote:
On Apr 14, 2007, at 3:14 PM, Geoffrey Garen wrote:
1.4
"when not qualified to explicitly refer"
when not qualified explicitly to refer
(split infinitive)
The split infinitive is not generally considered a grammatical
On Apr 15, 2007, at 11:15 AM, Jordan OSETE wrote:
Hello folks at the WHATWG.
Some simple suggestions about the great 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 pat
Yes, they could, just like storey buttons in the lift.
Chris
-Original Message-
From: Geoffrey Garen [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 15, 2007 8:32 PM
To: Kristof Zelechovski
Cc: [EMAIL PROTECTED]
Subject: Re: [whatwg] A few editing suggestions for the HTML5 spec
> Pressing
Methinks, if several buttons are pressed, the events should be placed in the
queue and executed in the order of appearance. If the page is reloaded as a
result of an event handler, all remaining events should be discarded as
usual.
I am not quite sure how to handle this situation because the user
Pressing a button when the user agent is in paused state should
cause the
button to remain pressed until the user agent wakes up and
execution of the
associated event handlers should be deferred.
So, if I had N buttons in a page, does that mean that all N could
potentially end up in a pres
Hello folks at the WHATWG.
Some simple suggestions about the great 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 back to a
