On Wed, 2010-11-03 at 23:21 -0400, Boris Zbarsky wrote:
> Curious. Firefox 4 in fact uses a delay-like setup for timeouts (used
> to use a clock-based one in 3.6 and earlier)
Ah! I was testing in an old beta (in an XP VirtualBox, plus with 3.6 on
Linux). Updated; confirmed Firefox does now f
On 11/3/10 11:01 PM, and-py wrote:
* When moving the clock forward, Firefox (4) and Safari (5) act
clock-based: they immediately fire any interval or timeout whose
deadline has passed, and continue calling intervals at their period
thereafter.
Curious. Firefox 4 in fact uses a delay-like setup
On Nov 3, 2010, at 8:01 PM, and-py wrote:
> Here's a curious little issue.
>
> When you use `setTimeout` or `setInterval`, the HTML5 spec seems to say
> that the callback should occur after a certain amount of actual time has
> elapsed.
>
> But what browsers might do is take the system clock, ad
Here's a curious little issue.
When you use `setTimeout` or `setInterval`, the HTML5 spec seems to say
that the callback should occur after a certain amount of actual time has
elapsed.
But what browsers might do is take the system clock, add the given
number of milliseconds and call back when tha
Hi,
Currently, when a radio button is required, it will suffer from being
missing if no radio elements in the radio button group is checked.
However, radio elements in the group will not suffer from being missing
if they do not have the required attribute. In other words, if you try
to style inval
