- From: Jim Jewett <jimjjewett@gmail.com>
- Date: Wed, 8 Apr 2009 12:12:20 -0400
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: HTML WG Public List <public-html@w3.org>
On 4/8/09, Boris Zbarsky <bzbarsky@mit.edu> wrote: > Jim Jewett wrote: >> It was rejected, because the browser makers refused. Their most >> clearly stated objection is that they couldn't come up with a >> reasonable User Interface. > I'm sorry, but can you point me to this discussion? Not at the moment; it may have even been in the xhtml 2 discussion list. I'll try to remember to search later. And of course, if *you* are questioning it, the opinions may have changed in the last year or two. >> Today's user interface has no nested hrefs > Really? Here's some markup that produces nested <a> elements in at > least Gecko and Opera: > http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Chtml%3E%0A%20%20%3Cbody%3E%0A%20%20%20%20%3Ca%3E%3Cspan%3E%3Ctable%3E%3Ctr%3E%3Ctd%3E%3Ca%3E%3C%2Fa%3E%3C%2Ftd%3E%3C%2Ftr%3E%3C%2Ftable%3E%3C%2Fspan%3E Im using Opera 9.64, and that it (says it) reparents the <table> as a sibling rather than a child of the <a>. > Yes, true. But HTML5 is defining the nested-href behavior anyway, since > it's trivial to get it in XHTML and not that hard to get it in HTML+DOM. There is a difference between defining error correction and supporting in a way that encourages use. -jJ
Received on Wednesday, 8 April 2009 16:13:00 UTC