Re: [whatwg] Questions about the progress element

[Jonas Sicking]

On Tue, Aug 3, 2010 at 6:06 PM, Ian Hickson i...@hixie.ch wrote:
 If it was up to me we'd just have all the numeric types be infinite
 precision in the spec and have the UAs compete on how good a tradeoff they
 can offer between precision and performance. :-)

That sounds like an interoperability nightmare. You'd get all sorts of
edge cases where x/y == z tests true or false depending on how much
precision the implementation uses.

/ Jonas

Re: [whatwg] Questions about the progress element

[Ian Hickson]

On Mon, 24 May 2010, Mounir Lamouri wrote:
 
 I'm wondering why the value and max IDL attributes have to reflect the 
 content attribute with zero as a default value instead of reflecting the 
 internal values used to calculate the position. Wouldn't that be easier 
 to know what is the internal value and max values by using the IDL 
 attributes ?

I've changed 'max' to default to 1 rather than 0, but in general I think 
we should avoid having magic in IDL attributes that reflect content 
attributes, as it leads to very strange behaviour.


 In addition, couldn't the position IDL attribute returns a double 
 instead of a float? As we are dividing two floats, the precision may be 
 helpful.

I don't really mind; what do implementors think makes most sense here?

If it was up to me we'd just have all the numeric types be infinite 
precision in the spec and have the UAs compete on how good a tradeoff they 
can offer between precision and performance. :-)

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

[whatwg] Questions about the progress element

[Mounir Lamouri]

Hi,

I'm wondering why the value and max IDL attributes have to reflect the
content attribute with zero as a default value instead of reflecting the
internal values used to calculate the position. Wouldn't that be easier
to know what is the internal value and max values by using the IDL
attributes ?

In addition, couldn't the position IDL attribute returns a double
instead of a float ? As we are dividing two floats, the precision may be
helpful.

Thanks,
--
Mounir