- From: Robin Berjon <robin@berjon.com>
- Date: Mon, 3 Oct 2011 14:29:26 +0200
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: "spec-prod\@w3.org Prod" <spec-prod@w3.org>
On Oct 3, 2011, at 14:12 , Norman Walsh wrote: > FYI: > > https://plus.google.com/105458233028934590147/posts/9qxYQ7RepSq > > It probably wouldn't be hard to fix the stylesheets, but I'm not even > sure where the HEAD of development is these days. In any event, it's > something to watch for no matter how you're producing your specs. As David points out, this is largely a problem due to serving XHTML as text/html. Going through all existing specifications to fix this would be painful, but it would probably be worth looking into catching this sort of problem in pubrules. You mention HEAD but not of what, I'm guessing XMLSpec? If so, I think that a recent discussion on the topic has shown that it's still rather widely used, but that every group using it seems to have its own branch. It probably wouldn't hurt for some brave Tzar to stand up and unify all those branches so that everyone can benefit from the same bugfixes (note that I'm not anywhere near volunteering for this). Notably, I'm not sure what the value of <h1><a id='foo'/>Foo</h1> is over <h1 id='foo'>Foo</h1> (or perhaps even more semantically: with the id on the containing <div>) is, but a fix replacing the former with the latter would address the reported bug (which has been there a while) for everyone at once. -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 3 October 2011 12:29:52 UTC