Hi Jere,
On Wed, Dec 3, 2008 at 8:38 AM, Jere Kapyaho <[EMAIL PROTECTED]> wrote:
> On 3.12.2008 4.51, "ext Marcos Caceres" <[EMAIL PROTECTED]> wrote:
>> Got a question... I've relaxed keyword attributes to be allowed to
>> have leading and trailing whitespace. Now, widget user agents are
>> requi
Hi Jonas,
On Wed, Dec 3, 2008 at 3:04 AM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
> On 12/2/08, Marcos Caceres <[EMAIL PROTECTED]> wrote:
>>
>> Got a question... I've relaxed keyword attributes to be allowed to
>> have leading and trailing whitespace. Now, widget user agents are
>> required to tr
HI Simon,
On Wed, Dec 3, 2008 at 8:25 AM, Simon Pieters <[EMAIL PROTECTED]> wrote:
> On Wed, 03 Dec 2008 03:51:13 +0100, Marcos Caceres
> <[EMAIL PROTECTED]> wrote:
>
>> Got a question... I've relaxed keyword attributes to be allowed to
>> have leading and trailing whitespace.
>
> Any particular
Hi Henri,
On Wed, Dec 3, 2008 at 8:14 AM, Henri Sivonen <[EMAIL PROTECTED]> wrote:
> On Dec 3, 2008, at 04:51, Marcos Caceres wrote:
>
>> So, for instance, is ok.
>>
>> Does anyone see any problem with this? Should I revert back to being
>> strict and having UA do comparisons without trimming?
>
On Dec 3, 2008, at 10:38, Jere Kapyaho wrote:
Based on that, it might be better to just *not* do it, but then you
wouldn't be XML compliant.
It's perfectly XML compliant to be DTDless, to let the XML processor
do its thing with the datatype defaulted to CDATA and not to perform
any trimm
On 3.12.2008 4.51, "ext Marcos Caceres" <[EMAIL PROTECTED]> wrote:
> Got a question... I've relaxed keyword attributes to be allowed to
> have leading and trailing whitespace. Now, widget user agents are
> required to trim whitespace prior to validation/processing. Widget
> user agents must only p
On Wed, 03 Dec 2008 03:51:13 +0100, Marcos Caceres
<[EMAIL PROTECTED]> 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 val
On Dec 3, 2008, at 04:51, Marcos Caceres wrote:
So, for instance, is ok.
Does anyone see any problem with this? Should I revert back to being
strict and having UA do comparisons without trimming?
Experience with HTML, SVG and MathML indicates that when trimming is
specified, implementors
Got a question... I've relaxed keyword attributes to be allowed to
have leading and trailing whitespace. 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 i
