- From: Chris Lilley <chris@w3.org>
- Date: Fri, 27 Feb 2004 14:59:26 +0100
- To: Jim Ley <jim@jibbering.com>
- Cc: www-svg@w3.org
On Friday, February 27, 2004, 2:36:26 PM, Jim wrote: JL> Chris Lilley <chris <at> w3.org> writes: |>> Also the sample and text includes "evt.progress", but the IDL, and attributes |>> description doesn't, just a loaded and a total. JL> | JL> |Yes, it didn't get updated in time. JL> Which is correct, progress or just loaded/total? You get all of them. Sometimes the size is known in advance (eg in HTTP, most of the time) other times not (in which case, total will be -1). 'ProgressEvent's are generated during loading (how often is up to the implementation). You must get events with progress values zero and one, and should get intermediate values too. Loaded and total are absolute, in bytes, while progress is relative 0.0 to 1.0 JL> (I really have no preference for either) |>> Like much of the current draft, this is very good, |>> but shouldn't it be something the DOM WG are improving? JL> | JL> | The DOM WG is turning into a pumpkin, JL> So I've since learnt. Yes I was sort of confusing the traits and the JL> normalisation stuff here, (although I'd not looked at 3 enough to note the JL> normalisation specifically) Dom Level 3 Core is really worth looking at, the more I study it the more its clearly better than Lavel 2. JL> I'm happy that the SVG do all this stuff which is JL> really the domain of other (albeit now defunct) WGs but I hope it does get JL> rolled into other WGs specs as relevant. Yes, and there will be some meetings at the tech plenary next week to discuss that. For example, other groups want namespace-aware XMLEvents, of a small, typed DOM for Mobile, or an XPath mobile subset. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
Received on Friday, 27 February 2004 08:59:26 UTC