[whatwg] RWD Heaven: if browsers reported device capabilities in a request header

divya manian divya.manian at gmail.com
Mon Feb 13 12:08:13 PST 2012

On Wed, Feb 8, 2012 at 2:41 AM, Henri Sivonen <hsivonen at iki.fi> wrote:
> On Tue, Feb 7, 2012 at 11:17 PM, divya manian <divya.manian at gmail.com> wrote:
>> This is the info I would love to see any time for my app to make the
>> kind of decision it should:
>> * connection speed: so I know how fast my resources can load, how quickly.
>> * bandwidth caps: so I know I shouldn't be sending HD images.
> How do you know that I don't want to use my bandwidth quota to see
> your site fully if I chose to navigate to it?

Sites like netflix.com would be able to send higher quality of videos
depending on what is available. The point is not to abuse bandwidth
quota but to provide the most minimal experience if the situation is

> Why should you drain my batter faster if the battery is more full?
> (For stuff like throttling down animation and XHR polling, the UA
> should probably prevent background tabs from draining battery even
> when the battery is near full regardless of whether the site/app is
> benevolently cooperative.)

To provide a better user experience so searches and actions can happen
more quickly than in a very constrained environment.

> --
> Henri Sivonen
> hsivonen at iki.fi
> http://hsivonen.iki.fi/

More information about the whatwg mailing list