10602 2010-09-11 18:15:32 +0000 No boundary behavior specified for playbackRate/defaultPlaybackRate 2010-10-04 14:47:51 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All AIX RESOLVED WONTFIX P3 normal --- 1 franko ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 38883 0 franko 2010-09-11 18:15:32 +0000 In 4.8.9.8, "The playbackRate attribute gives the speed at which the media resource plays, as a multiple of its intrinsic speed. If it is not equal to the defaultPlaybackRate, then the implication is that the user is using a feature such as fast forward or slow motion playback. The attribute is mutable: on getting it must return the last value it was set to, or 1.0 if it hasn't yet been set; on setting the attribute must be set to the new value, and the playback must change speed (if the element is potentially playing)." The range of valid values for playbackRate is not specified; No behavior is defined for when defaultPlaybackRate or playbackRate are set to the values "Infinity" and "-Infinity". SUGGESTED CHANGE: When playbackRate is the positive Infinity value, current playback position of the media element must be the last position in its seekable time range. Coversely, when playbackRate is the negative Infinity value, current position must be the first position in its seekable time range. 39646 1 ian 2010-09-28 04:41:25 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: The spec says: "Except where otherwise specified, if an IDL attribute that is a floating point number type (double) is assigned an Infinity or Not-a-Number (NaN) value, a NOT_SUPPORTED_ERR exception must be raised." So the boundary case described above can never occur.