- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 04 Apr 2010 12:36:31 +0200
- To: Ian Hickson <ian@hixie.ch>
- CC: Anne van Kesteren <annevk@opera.com>, Kornel Lesinski <kornel@geekhood.net>, public-html@w3.org
On 04.04.2010 00:38, Ian Hickson wrote: > On Sat, 3 Apr 2010, Julian Reschke wrote: >> On 04.04.2010 00:34, Anne van Kesteren wrote: >>> On Sat, 03 Apr 2010 02:00:32 -0700, Julian Reschke >>> <julian.reschke@gmx.de> wrote: >>>> The attribute is an HTML attribute, but it's value space is defined by >>>> the HTTP header registry. >>>> >>>> Changing this in general *will* cause objections (yes, those). >>> >>> Please stop the drama. In the ten years it was deployed it was never >>> implemented as HTML4 specified. No wonder its semantics are being >>> changed to match reality. >> >> I was just stating a fact. >> >> The fact that browsers do not implement this doesn't mean it isn't used >> in documents. > > Browsers _do_ implement it, contrary to HTML4, which intends it for > servers, who don't implement it. You may wish to recheck your facts. By "it" I meant http-equiv in general, not specifically Content-Language. I have no problems with the spec stating the facts (how UAs actually use http-equiv/C-L, as long as it's accurate). What I have a problem with is taking over a value space *in general* which previously was defined to be the same as for HTTP headers. > ... > some people will object (indeed, you have already objected). What matters > isn't whether anyone agrees, what matters is that we make the right > technical decisions that are compatible with reality. > ... Yes, it would be nice if we had someone who makes the right technical decisions without any of these time consuming discussions. But that person doesn't exist, so we're stuck with doing exactly what we're doing right now. Best regards, Julian
Received on Sunday, 4 April 2010 10:37:07 UTC