W3C home > Mailing lists > Public > public-html@w3.org > July 2008

Re: On ISSUE-41: Decentralized extensibility

From: Thomas Broyer <t.broyer@gmail.com>
Date: Mon, 21 Jul 2008 11:12:18 +0200
Message-ID: <a9699fd20807210212i7fa506cdo1e1f97a370167382@mail.gmail.com>
To: "Chris Wilson" <Chris.Wilson@microsoft.com>
Cc: "public-html@w3.org" <public-html@w3.org>

On Mon, Jul 21, 2008 at 4:34 AM, Chris Wilson
<Chris.Wilson@microsoft.com> wrote:
> http://msdn.microsoft.com/en-us/library/ms531426.aspx#Creating_Custom_Element is the best reference I could find.

Sigh. Being a "user" doc, it doesn't deal with how mismatched tags are
handled (you're supposed to match your tags after all)

Would it mean you do not have any internal doc that could be published
as a white-paper of some sort?

> From memory - /> never signals an empty element to us - we always, I think, required a close tag.

That's not what the above linked document says ;-)
http://msdn.microsoft.com/en-us/library/ms531426.aspx#ParsingEBTags

>  And we didn't really check "wellformed" very well.  :(

Of course, and that's kind of a feature IMO (remember XML5? "XML with
error recovery"?); my question was "what does IE do with
"non-wellformed" content?".
See the last 4 lines of http://www.ltgt.net/ie-namespace-tests.html
for "empirical reverse engineering".
There are obvious missing tests here, re how HTML tags like P or
TABLE, or "formatting elements" behave wrt "custom elements": do <p>
or <table> imply end tags for custom elements? how about </p> ? and
unmatched <b> or <i> in the middle of unmatched custom elements? etc.
I'll try to find time to update the page with such tests (and try to
fix the page so that "view source" shows the actual source, not the
generated one)

-- 
Thomas Broyer
Received on Monday, 21 July 2008 09:12:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:56 UTC