Update all float attributes in HTMLMediaElement and related objects to double

Source/WebCore/html/HTMLMediaElement.idl

Index: Source/WebCore/html/HTMLMediaElement.idl
diff --git a/Source/WebCore/html/HTMLMediaElement.idl b/Source/WebCore/html/HTMLMediaElement.idl
index 8d658c0d00848536484b1ef7f858a2be81e3a78c..cb3750d451a60ae7bc72c0996dd94c03494bee7b 100644
--- a/Source/WebCore/html/HTMLMediaElement.idl
+++ b/Source/WebCore/html/HTMLMediaElement.idl
@@ -62,14 +62,14 @@ readonly attribute unsigned short readyState;
 readonly attribute boolean seeking;
 
 // playback state
-attribute float currentTime
+attribute double currentTime
     setter raises (DOMException);
 readonly attribute double initialTime;
-readonly attribute float startTime;
-readonly attribute float duration;
+readonly attribute double startTime;

[eseidel, 2013/04/05 21:44:14]

This is a web-observable change, no?  I guess all numbers in JS are doubles
anyway?

[acolwell GONE FROM CHROMIUM, 2013/04/05 22:29:11]

Yes it is observable. If you set any of these properties with extreme values
then they get truncated to the float range. This causes the following code to go
BOOM().

video.playbackRate = Number.MAX_VALUE
if (video.playbackRate != Number.MAX_VALUE)
  BOOM();

This change is really just about making HTMLMediaElement conform to the HTML5
spec and avoid these truncations to the float range.

+readonly attribute double duration;
 readonly attribute boolean paused;
-attribute float defaultPlaybackRate;
-attribute float playbackRate;
+attribute double defaultPlaybackRate;
+attribute double playbackRate;
 readonly attribute TimeRanges played;
 readonly attribute TimeRanges seekable;
 readonly attribute boolean ended;
@@ -80,7 +80,7 @@ void pause();
 
 // controls
 attribute boolean controls;
-attribute float volume 
+attribute double volume 
     setter raises (DOMException);
 attribute boolean muted;
 attribute [Reflect=muted] boolean defaultMuted;