On Tue, 6 Apr 2010, Tab Atkins Jr. wrote:
>
> The proposal is to mandate that expose some sort of
> "clear" widget in itself, which fires an appropriate event when the user
> activates it.
It already does -- the event is "input" and in the case you describe, it
would fire with value == "".
>
On Tue, Apr 6, 2010 at 8:32 AM, Tab Atkins Jr. wrote:
> On Tue, Apr 6, 2010 at 2:00 AM, Ian Hickson wrote:
>> Well you currently can do this by using the onbeforeprint and onafterprint
>> hooks, though that's not exactly pretty. Hopefully it will also be
>> possible with media-specific CSS, thoug
On Tue, Apr 6, 2010 at 9:55 AM, Anne van Kesteren wrote:
> On Tue, 06 Apr 2010 17:32:49 +0200, Tab Atkins Jr.
> wrote:
>>
>> On Tue, Apr 6, 2010 at 2:00 AM, Ian Hickson wrote:
>>>
>>> Well you currently can do this by using the onbeforeprint and
>>> onafterprint
>>> hooks, though that's not exac
On Tue, 06 Apr 2010 17:32:49 +0200, Tab Atkins Jr.
wrote:
On Tue, Apr 6, 2010 at 2:00 AM, Ian Hickson wrote:
Well you currently can do this by using the onbeforeprint and
onafterprint
hooks, though that's not exactly pretty. Hopefully it will also be
possible with media-specific CSS, though
On Tue, Apr 6, 2010 at 2:00 AM, Ian Hickson wrote:
> Well you currently can do this by using the onbeforeprint and onafterprint
> hooks, though that's not exactly pretty. Hopefully it will also be
> possible with media-specific CSS, though that depends on how
> ends up working in CSS. If this pro
On Thu, 21 Jan 2010, NARUSE, Yui wrote:
> In 4.10.19.4 URL-encoded form data, The
> application/x-www-form-urlencoded encoding algorithm,
> it says:
>
> > For each character in the entry's name and value, apply the following
> > subsubsteps:
> >
> > If the character isn't in the range U+0020, U+0
