Re: [whatwg] Time Parsing

2012-01-11 Thread Ian Hickson
On Wed, 11 Jan 2012, Ian Hickson wrote: > On Wed, 15 Jun 2011, Lachlan Hunt wrote: > > On 2011-06-15 07:55, Ian Hickson wrote: > > > On Mon, 28 Mar 2011, Lachlan Hunt wrote: > > > > This should also only allow up to 3 digits representing > > > > milliseconds. If there are 4 or more digits (microse

Re: [whatwg] Time Parsing

2012-01-11 Thread Ian Hickson
On Wed, 15 Jun 2011, Lachlan Hunt wrote: > On 2011-06-15 07:55, Ian Hickson wrote: > > On Mon, 28 Mar 2011, Lachlan Hunt wrote: > > > This should also only allow up to 3 digits representing > > > milliseconds. If there are 4 or more digits (microseconds or > > > beyond), the spec should state tha

Re: [whatwg] should we add beforeload/afterload events to the web platform?

2012-01-11 Thread Boris Zbarsky
On 1/11/12 6:59 AM, Simon Pieters wrote: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1297 Might not be cross-browser yet (e.g. Opera seems to run the image's onload handler), but should work per spec I think. Well, the load can't be prevented if it's speculatively loaded it befor

Re: [whatwg] should we add beforeload/afterload events to the web platform?

2012-01-11 Thread Simon Pieters
On Tue, 10 Jan 2012 07:34:19 +0100, Boris Zbarsky wrote: On 1/10/12 1:02 AM, Boris Zbarsky wrote: I'd like to understand the client-side transformation use-case better, in particular. What is it really trying to do? OK, I got more context on this. The goal of the client-side transformatio