Re: Http header including if ECMA (Javascript) is on and the version

[Philipp Junghannß <[e-mail]>]

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
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.

2016-10-08 8:12 GMT+02:00 Kari hurtta <[e-mail]>:

> >   Perhaps a new section between 7 & 8 as follows;
> >
> > 8. The ECMA script (Javascript) Client Hint
> >
> > The "ECMA" request header field is a number or text that
> > indicates the client's current ECMA implementation version. A blank ECMA
> > hint would indicate that ECMA script is currently turned off.
> > ECMA = Text [32 ASCII characters]
> >
> > If ECMA occurs in a message more than once, the last value
> > should be used to override other occurrences.
>
>
> Seems good idea, but is there really need for ECMA version?
>
> If no, then maybe:
>
>   The "ECMA" request header field indicates the client's
>   ECMA script execution is turned on or off.
>
>     ECMA = "on" / "off"
>
>   If "ECMA" request header field includes invalid or
>   unknown value, this is interpretes as ECMA script execution
>   is turned on.
>
> / Kari Hurtta
>
>