[Bug 26132] New: Add "metered-network-autoplay" attribute to <HTML> tag with values that will help browser to restrict autoplay based on available bandwidth.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26132

            Bug ID: 26132
           Summary: Add "metered-network-autoplay" attribute to <HTML> tag
                    with values that will help browser to restrict
                    autoplay based on available bandwidth.
           Product: HTML WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: sridhar1803@live.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

All of the mobile browser providers have disabled the 'autoplay' behaviour in
the mobile browsers since there is a high likelihood of mobile devices using
metered networks. This does not leave the developers with a choice to autoplay
media content on the devices. Game developers could find this especially
restrictive for providing the right user experience. Not insignificant 
proportion of mobile device usage happens over unmetered network and having an
option to autoplay media on mobile devices is quite useful. My proposal is to
add an attribute to the HTML tag of a webpage, value of which will determine if
media tags which have autoplay="true" can be auto played, based on the type of
the network (as provided by Network Information API -
https://dvcs.w3.org/hg/dap/raw-file/tip/network-api/Overview.html#idl-def-NetworkInformation) 

example : 

<HTML metered-network-autoplay="false">
<HTML metered-network-autoplay="true">

Default value for the metered-network-autoplay attribute will be "false" .

If this is implemented, webpage developers can provide better user experience
where network permits.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 18 June 2014 07:58:42 UTC