W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2008

Re: [widgets] Trimming attribute values, a bad idea?

From: Simon Pieters <simonp@opera.com>
Date: Wed, 03 Dec 2008 09:25:49 +0100
To: "Marcos Caceres" <marcosscaceres@gmail.com>, public-webapps <public-webapps@w3.org>
Message-ID: <op.ulku1ba5idj3kv@hp-a0a83fcd39d2>

On Wed, 03 Dec 2008 03:51:13 +0100, Marcos Caceres  
<marcosscaceres@gmail.com> wrote:

> Got a question... I've relaxed keyword attributes to be allowed to
> have leading and trailing whitespace.

Any particular reason for this? :-)

> Now, widget user agents are
> required to trim whitespace prior to validation/processing. Widget
> user agents must only perform literal comparisons with trimmed values,
> and must not perform case insensitive comparisons.

In HTML5, enumerated attributes are ASCII case-insensitive with no leading  
or trailing whitespace allowed.

I'm not sure how SVG and MathML handle enumerated attributes, though.

Simon Pieters
Opera Software
Received on Wednesday, 3 December 2008 08:26:33 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:13 UTC