Re: [whatwg] progress draft

2006-03-28 Thread Ian Hickson
Based on everyone's feedback, I've removed the ability to use % in value= attribute values for progress and meter. This simplified the processing model quite a bit. You can still use percentages (and per-mille, and so forth) if you put the content in-line, which is the recommended behaviour:

Re: [whatwg] progress draft

2006-03-28 Thread Ric Hardacre
Ian Hickson wrote: [snip] This seems to be a case where there should be one, and preferably only one, obvious way to do it holds. Well, there are two ways -- update the textContent, and update the attribute. But for the attribute, there's only one syntax. We could remove the attribute as

Re: [whatwg] progress draft

2006-03-28 Thread Simon Pieters
Hi, From: Ian Hickson [EMAIL PROTECTED] Well, there are two ways -- update the textContent, and update the attribute. But for the attribute, there's only one syntax. We could remove the attribute as well, and force authors to use textContent, though... I think it's good to have a value=

Re: [whatwg] progress draft

2006-03-28 Thread Alexey Feldgendler
On Tue, 28 Mar 2006 17:49:15 +0800, Simon Pieters [EMAIL PROTECTED] wrote: I think it's good to have a value= attribute, because you might want to have both plain text and an indicator, as can be seen in Hotmail: p12% of 250 MB meter value=0.12/meter/p I think CSS is more appropriate

Re: [whatwg] progress draft

2006-03-28 Thread Ric Hardacre
Matthew Paul Thomas wrote: On Mar 28, 2006, at 9:05 PM, Ric Hardacre wrote: Ian Hickson wrote: ... The only difference between meter and progress is the potential for progress to be dynamic. That's a big difference. It means the UI for one has to show that it is static, and the UI for

Re: [whatwg] progress draft

2006-03-28 Thread mozer
Hello I18N Matter for Progress: The spec says : If the value attribute is omitted, then user agents must also parse the textContent of the progress element in question using the steps for finding one or two numbers in a string . These steps will return nothing, one number, one number with a

Re: [whatwg] progress draft

2006-03-28 Thread fantasai
Ian Hickson wrote: On Tue, 28 Mar 2006, fantasai wrote: Another issue is the possible use of U+2212 MINUS SIGN intead of U+002D HYPHEN-MINUS. This last, at least, should be handled whenever the number is parsed from the text content rather than in an attribute. In the text, negative

Re: [whatwg] progress draft

2006-03-25 Thread Henri Sivonen
On Mar 25, 2006, at 12:11, Michael 'Ratt' Iannarelli wrote: Having two elements that represent pretty much the same thing, (a progress bar is a type of meter after all), is redundant. It isn't redundant when they are not the same thing. They are not the same thing here. Have you read

Re: [whatwg] progress draft

2006-03-25 Thread Michael 'Ratt' Iannarelli
Greetings, Henri Sivonen wrote: It isn't redundant when they are not the same thing. They are not the same thing here. Have you read mpt's earlier posts on the topic? http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2004-September/002211.html Yes, I have read mpt's (and others')

Re: [whatwg] progress draft

2006-03-24 Thread Simon Pieters
Hi, From: Ian Hickson [EMAIL PROTECTED] What do people think? Is it valuable to be able to do: progress value=5%/ ...instead of either of these: progress value=0.05/ progress5%/progress ...? No, direct relationship to the DOM makes implementation and authoring more straight