Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Harmonizing HTML and XHTML selector behavior

2 views
Skip to first unread message

Henri Sivonen

unread,
Apr 6, 2009, 5:55:19 AM4/6/09
to
On public-html, the issue of how to deal with both upper-case selectors
matching HTML nodes on one hand and with camelCase selectors matching
SVG camelCase nodes in the same tree on the other hand converged on
making selectors have two internal local name atoms: one that is
ASCII-lowercased and is used when compared against HTML nodes and
another that is in the original case and used for comparing against
other element nodes.

http://lists.w3.org/Archives/Public/public-html/2009Apr/0081.html

If this is indeed the solution that gets implemented for HTML documents,
is there any good reason to make the behavior conditional on the
document being an HTML document?

That is, is there then any good reason not to use the ASCII lower-cased
selector ident when comparing against XHTML nodes as well and adjusting
specs accordingly thereby eliminating a useless difference between HTML
and XHTML and simplifying implementation?

(This would make nodes in the XHTML namespace that have upper-case ASCII
letters in their local name unmatchable with selectors in both XHTML and
HTML. Such nodes are already unmatchable in HTML documents in Gecko and
WebKit and have never been conforming or useful in XHTML.)

--
Henri Sivonen
hsiv...@iki.fi
http://hsivonen.iki.fi/

fantasai

unread,
Apr 22, 2009, 12:38:13 PM4/22/09
to Henri Sivonen

Hi Henri,

I think you want m.d.platform, not this group (m.d.t.css).

~fantasai

0 new messages