On Sat, 4 Feb 2006, Bjoern Hoehrmann wrote:
If the concern here is what the specification should say, then that's
what a valid state is, not what a valid document is, since the class of
predictably valid documents does not cover many dynamic documents.
That makes sense. I'm not sure what
* Ian Hickson wrote:
Well, if you approach the problem by asking whether it's possible that
things become non-compliant, you'll either have to analyze any and all
dependencies like server-side scripts and workflows or you'd generate
false negatives, since adding some external data to the
Hi,
From: Gervase Markham [EMAIL PROTECTED]
It's much harder to spot them when they are dynamically generated by
e.g. a cloneNode operation. You can't submit your browser's DOM tree to
the validator...
Browsers could mark all errors as red in view source. In Firefox you can
select a piece of
Simon Pieters wrote:
Browsers could mark all errors as red in view source. In Firefox you can
select a piece of text and view selection source, which will bring up
the serialized DOM.
They could (at least, as far as I understand the issue), for XHTML at
least (not HTML5), if they wanted to
Gervase Markham wrote:
Lachlan Hunt wrote:
Errors caused by the result of duplicate IDs either in the markup or
indirectly as a result of badly nested elements can be fixed by a quick
visit to the validator (or other conformance tool) or by making use of
any or all of those tools I mentioned
Blanchard, Todd wrote:
Any markup that causes a browser to automatically clone a node will
be non-conformant and will be flagged as erroneous by a validator.
You are assuming that validators run javascript - they generally
don't.
I'm well aware that validators don't run JavaScript and I'm
On Thu, 2 Feb 2006, Blanchard, Todd wrote:
What I want to know is: if the cloned node has an id attribute, and
id is meant to be unique, then how do we resolve this conflict?
We don't. For compatibility with existing implementations we are forced to
require that the ID be duplicated too.
On Thu, 2 Feb 2006, David Hyatt wrote:
BTW, we tried to add span as an inline that should be reopened (like
font and b etc.) and it broke some of our layout tests (snippets of
real-world Web sites). span clearly does not always reopen in WinIE
and Firefox, so for now we are having to
On Thu, 2 Feb 2006, Blanchard, Todd wrote:
OK, I have to disagree with this - the id's MUST NOT be duplicated as
the end result is simply converting one kind of error to a different
kind of error.
I don't understand why this is bad. The document isn't even well-formed in
these cases, if
On Fri, 3 Feb 2006, Blanchard, Todd wrote:
You are assuming that validators run javascript - they generally don't.
I'm hoping to add it to Scrutinizer
(http://www.blackbagops.net/seaside/html) but that would make it unique
in the world of validators.
It's mathematically impossible to
* Ian Hickson wrote:
On Fri, 3 Feb 2006, Blanchard, Todd wrote:
You are assuming that validators run javascript - they generally don't.
I'm hoping to add it to Scrutinizer
(http://www.blackbagops.net/seaside/html) but that would make it unique
in the world of validators.
It's
On Sat, 4 Feb 2006, Bjoern Hoehrmann wrote:
It's mathematically impossible to verify that all script on the page is
always going to generate conformant DOMs, but indeed, a validator that
attempts it should be given high marks.
Well, if you approach the problem by asking whether it's
.
-Todd Blalnchard
-Original Message-
From: [EMAIL PROTECTED] [mailto:whatwg-
[EMAIL PROTECTED] On Behalf Of Ian Hickson
Sent: Friday, January 27, 2006 6:12 PM
To: [EMAIL PROTECTED]
Subject: [whatwg] Update to the Adoption Agency Algorithm
Just a note to those of you who reviewed
Blanchard, Todd wrote:
Lachlan Hunt wrote:
Blanchard, Todd wrote:
What I want to know is: if the cloned node has an id
attribute, and id is meant to be unique, then how do we resolve
this conflict?
The ID attributes need to be duplicated in such cases, that's what
existing browsers do.
David Hyatt wrote:
BTW, we tried to add span as an inline that should be reopened (like
font and b etc.) and it broke some of our layout tests (snippets
of real-world Web sites). span clearly does not always reopen in
WinIE and Firefox, so for now we are having to leave it out.
It never
Just a note to those of you who reviewed the new parsing rules yesterday:
I changed them today to take into account some feedback from Hyatt.
Basically the old algorithm was creating too many nodes. This is now
fixed, the algorithm only moves the nodes that are being closed, not the
other
16 matches
Mail list logo
