- From: Giovanni Campagna <scampa.giovanni@gmail.com>
- Date: Mon, 4 May 2009 19:18:19 +0200
- To: Ian Hickson <ian@hixie.ch>
- Cc: Maciej Stachowiak <mjs@apple.com>, "public-webapps@w3.org Group WG" <public-webapps@w3.org>
2009/5/4 Ian Hickson <ian@hixie.ch>: > On Mon, 4 May 2009, Giovanni Campagna wrote: >> 2009/5/4 Ian Hickson <ian@hixie.ch>: >> > On Fri, 3 Oct 2008, Maciej Stachowiak wrote: >> >> >> >> I would recommend to the HTML5 editor to require some reasonable minimum >> >> because it seems to be de facto required for Web compatibility. I cannot >> >> state with certainty that nothing lower than 10ms is safe. Chrome >> >> shipped with a 1ms delay and that was found to create problems on a >> >> number of sites, including nytimes. They are planning to try 4ms next. >> >> We would consider using a lower limit in the official webkit.org version >> >> of WebKit, not not as low as 1ms. >> > >> > I've used 4ms for now but will increase it if that is found to be too low. >> > >> > I used 10ms for setInterval(). >> >> I would like to see a maximum too, as well as clearly defined error >> behavior for values outside the allowed range. This because I found >> very strange when Firefox turned an infinite timeout into 1ms. > > The spec already defines this actually. Sorry, my mistake: I wrote infinite, but I actually meant really long but inside the range of a valid integer. > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' > Giovanni
Received on Monday, 4 May 2009 17:19:00 UTC