[Bug 11602] <video> define precisely how autoplay overrides preload

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11602

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
          Component|Test Suite                  |HTML5 spec (editor: Ian
                   |                            |Hickson)
                 CC|                            |ian@hixie.ch
         AssignedTo|zhihengw@google.com         |ian@hixie.ch
         Resolution|                            |WONTFIX
          QAContact|zhihengw@google.com         |public-html-bugzilla@w3.org
            Summary|define precisely how        |<video> define precisely
                   |autoplay overrides preload  |how autoplay overrides
                   |                            |preload
            Product|Web Performance             |HTML WG

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-02 23:36:13 UTC ---
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 behaviour for preload="" is intentionally entirely undefined, it's a hint
only.

The behaviour of buffering is intentionally mostly undefined, it's a quality of
implementation issue.

The behaviour of autoplay="" is intentionally partially undefined, UAs can
override it.

I don't see how I could possibly precisely define the interaction of these
three issues. It would depend entirely on the implementation goals. For
example, if the UA always ignored autoplay="" and preload="" and required the
user to give explicit permission for every 10 bytes that were buffered, the
answer regarding how they would interact would be radically different than if
the UA ignored preload="", always buffered everything aggressively at the first
possible opportunity, and autoplayed if the attribute was present. Most UAs
will hopefully be in between these, but the situation is still that this is
essentially intentionally undefined.

Having said that, if there is a specific question you had in mind, please let
me know (and reopen this bug). I'm happy to add non-normative text that tries
to give guidance on this.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 2 June 2011 23:36:15 UTC