Since UAs handle whitespace in the id attribute inconsistently (see
below), old specs imply or require whitespace trimming and ids with
whitespace are unreferencable from whitespace-separated lists of ids,
I suggest adding the following language concerning document conformance:
The value
Quoting Henri Sivonen [EMAIL PROTECTED]:
Also, I suggest requiring that elements must not have both id and
xml:id and requiring that xml:id must not occur in the HTML
serialization. (Again, from the document conformance point of view--
not disputing requirements on browsers.)
How could it
Henri Sivonen wrote:
Since UAs handle whitespace in the id attribute inconsistently (see
below), old specs imply or require whitespace trimming and ids with
whitespace are unreferencable from whitespace-separated lists of ids, I
suggest adding the following language concerning document
Quoting fantasai [EMAIL PROTECTED]:
I'd rather see the id attribute restricted to an NCName token insofar
as possible. We can make an exception for Hixie's repetition templates,
but otherwise I think it should be compatible with the XML ID syntax.
I agree. Note also that the repetition
On Apr 2, 2006, at 19:26, Anne van Kesteren wrote:
I agree. Note also that the repetition template also allows for
characters that
are compatible with XML ID. Of course, this is only for valid
documents... All
things should still be defined in a way that they take into account
invalid,
Henri Sivonen wrote:
On Apr 2, 2006, at 18:56, fantasai wrote:
I'd rather see the id attribute restricted to an NCName token insofar
as possible. We can make an exception for Hixie's repetition templates,
but otherwise I think it should be compatible with the XML ID syntax.
Do you mean
I've run into some issues with textareas and after checking
http://www.w3.org/Submission/web-forms2/ and seeing that the mailing list is
active...
1. I always thought that cols, which has been around forever, was advisory
regarding width, in
the sense that if there was no other overriding