- From: Anne van Kesteren <annevk@opera.com>
- Date: Mon, 13 Feb 2012 21:02:53 +0100
On Mon, 13 Feb 2012 20:46:57 +0100, Anne van Kesteren <annevk at opera.com> wrote: > The list starts with <a> and the moment you do not use UTF-8 (or UTF-16, > but you really shouldn't) you can run into problems. I wonder how > controversial it is to just require UTF-8 and not accept anything else. I guess one could argue that <a> is already captured by the requirements around URL validation. That would leave <form> and potentially some script-related features. It still seems sensible to me to flag everything that is not labeled as UTF-8, but if we want something intermediate we could start by flagging non-UTF-8 pages that use <form> and maybe obsolete <form accept-charset> or obsolete any other value than utf-8 (I filed a bug on that feature already to at least restrict it to a single value). -- Anne van Kesteren http://annevankesteren.nl/
Received on Monday, 13 February 2012 12:02:53 UTC