- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 2 Sep 2009 23:35:59 +0000 (UTC)
On Sat, 29 Aug 2009, ?istein E. Andersen wrote:
>
> As far as I can tell, vertical tab ('\v') is not defined as a space
> character anymore, but does not cause a parse error either (unlike other
> control characters). Is this intentional?
It seems to cause a parse error... did I miss something?
> In IE7, IE8 and Safari, '\v' is handled as a space character in the
> sense that it can be used to separate attributes, but this is probably
> not important, and HTML5 does not seem to prevent browsers from handling
> '\v' as white space in text content anyway. I am sure you have a good
> reason for not defining '\v' as a space character, but would it not be
> more consistent to treat form feed ('\f') in the same way? (Firefox
> handles both as non-space characters, IE and Safari handle both as space
> characters, and handling these two slightly exotic C0 white-space
> characters differently seems surprising.)
Form Feeds are much more common, e.g. in RFC text/plain files.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 2 September 2009 16:35:59 UTC