- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 16 Dec 2010 09:14:49 +0100
- To: Mark Nottingham <mnot@mnot.net>
- CC: Maciej Stachowiak <mjs@apple.com>, Adam Barth <ietf@adambarth.com>, "Jungshik Shin (신정식, 申政湜)" <jungshik@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 16.12.2010 08:01, Mark Nottingham wrote: > Yes, I'm passingly familiar with the phenomenon. ;) > > What I meant was that browsers can stage the changes over a few versions (as you suggest), e.g., bringing up a console warning and talking about it in their roadmap. > > If desirable, we could reflect this in the spec by deprecating it and suggesting a warning now, and then disallowing it when the document progresses on the standards track. We can't deprecate something that was never allowed. We *can* warn that some UAs implement this. Best regards, Julian
Received on Thursday, 16 December 2010 08:15:33 UTC