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

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

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Wed, 3 Dec 2008 11:42:36 +0000
Message-ID: <b21a10670812030342k20def110xc4a288e2fc372d05@mail.gmail.com>
To: "Simon Pieters" <simonp@opera.com>
Cc: public-webapps <public-webapps@w3.org>

HI Simon,

On Wed, Dec 3, 2008 at 8:25 AM, Simon Pieters <simonp@opera.com> wrote:
> 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? :-)
>

Just to be nicer to authors.

>
>> 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.
>

Ok, I'll follow HTML5 on this.

-- 
Marcos Caceres
http://datadriven.com.au
Received on Wednesday, 3 December 2008 11:43:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:28 GMT