- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Fri, 6 Jul 2007 13:41:41 +0300
- To: joshue.oconnor@cfit.ie
- Cc: "public-html@w3.org WG" <public-html@w3.org>
On Jul 6, 2007, at 13:17, Joshue O Connor wrote: > Henri Sivonen wrote: >> <image> comes with a legacy parsing quirk attached to it. (As has >> already been pointed out many times.) > > Thanks Henri, it may have been pointed out many times but it is > still not clear, I honestly don't know how to make it clearer. The de facto way the start tag <image> is handles is entrenched (and not open for debate considering our draft design principles). If you want an element for still images (or anything else) that doesn't behave exactly like <img> in the text/html serialization, the element names "img" and "image" are out of the consideration. There's an infinite number of potential names that don't carry this baggage, such as "picture" and "graphic". > and with all due respect I have not got a clue what a 'legacy > parsing fork' is but I guess I can't eat my dinner with it. A legacy parsing *quirk* is a weird thing in parsing that browsers have to implement in order to work with legacy content out there. It follows that non-browser UAs need to implement them, too. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Friday, 6 July 2007 10:41:58 UTC