W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

The Downlink Client Hint | Re: Http header including if ECMA (Javascript) is on and the version

From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Date: Sat, 8 Oct 2016 20:18:31 +0300 (EEST)
Message-Id: <201610081718.u98HIVrn014854@shell.siilo.fmi.fi>
To: Philipp Junghannß <teamhydro55555@gmail.com>
CC: Kari hurtta <hurtta-ietf@elmme-mailer.org>, HTTP working group mailing list <ietf-http-wg@w3.org>, Scott Morgan <scott@adligo.com>
Philipp Junghannß <teamhydro55555@gmail.com>: (Sat Oct  8 17:38:09 2016)
> while the idea is generally not bad, there's one thing that might make it
> even better. if the browser could tell the server that it's on a slow
> connection (e.g. mobile internet throttled down to 32kbit/s, no joke) and

There is:

6.  The Downlink Client Hint

|   The "Downlink" request header field is a number that indicates the
|   client's maximum downlink speed in megabits per second (Mbps), as
|   defined by the "downlinkMax" attribute in the W3C Network Information
|   API ([NETINFO]).

/ Kari Hurtta

> the server could say that most of the important things are done serverside
> or HTML/CSS only and doing as little js as possible and maybe not use any
> large frameworks like jquery and whatever, because at least I get
> especially frustrated a lot when there's a javascript submit button which
> literally doesnt work because either the script is still loading or simply
> has failed to load which results in copy all the text (if its only one box)
> refresh, paste (or retype everything again) and hope the button works this
> time.
> because noscript and stuff doesnt work if the JS is activated in the
> browser but e.g fails to load.
Received on Saturday, 8 October 2016 17:19:04 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 8 October 2016 17:19:05 UTC