Anne van Kesteren

Damn bugs!

I wanted to make a single DTD with the minimum of contents. Within that DTD an external, by the W3C defined, DTD should be included and a rule, which I made, should be added. That looks like this:


This validates perfectly, but Mozilla does return a parse error. Is the validator wrong or is Mozilla wrong? I can't find any bugs related to this issue. I also made a test case for XHTML1.0 Strict with the id attribute applied on the head element (not that it makes sense), I get the same problem there, so I think it hasn't anything to do with the modularization of XHTML.

Does anyone know the Mozilla bug or the possible validator, which is troubling me?

I removed some files, some IRIs that are broken are removed.


  1. This has probably something to do with bug 69799:

    Posted by Martijn at

  2. Shouldn't the second line be &XHTMLDTD; (ampersand instead of a percent sign at the beginning)?

    Posted by David at

  3. David,
    It is a DTD, not an XML file ;).

    Posted by Anne at

  4. Does Mozilla download your custom DTD? If not, that's might have a result on this error??

    David: good to see you here mate :D

    Posted by Mark Wubben at

  5. Sure, Safari's fine now. ;-)

    The different ways different browsers handle code never ceases to amaze me.

    IE recognizes acronym, but not abbr; Gecko-based browsers underline both and provide tooltips; Safari italicizes both but doesn't provide a tooltip (or anything in the status bar) to show the title.

    Camino simply ignores this:

     font-weight: 600;

    Make a heading (h1 to h6) into a link and Camino will 'un'bolden it, too. Camino also has a very bright display:

    Ben's page, for example, which uses pale colours, is unreadable in it.

    I do like to have plenty of choice, but it does bring its own problems.

    I made a test page for smallcaps:

    Posted by Michael at

  6. It is a DTD, not an XML file ;).

    Oops, thought entitites were always written the same :)

    David: good to see you here mate :D

    Yea, you showed me the place :)

    Posted by David at

  7. Michael,
    Don't use <!-- comment --> in your inline style sheet. I've you ever going to send that page as application/xml you will understand why ;).

    (For the record: standard-compliant browsers will ignore everything inside those comments when they are in XML rendering mode.)

    Posted by Anne at

  8. Thanks for that, Anne.

    I haven't had the experience of doing that yet. :-) One sees that form around, and I thought Tidy added them too, which was why I did it. But checking that I see it only adds CSS comment tags.

    Posted by Michael at