- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 23 Jun 2016 16:31:14 +0000
- To: Joseph Scheuhammer <clown@alum.mit.edu>, Marco Zehe <mzehe@mozilla.com>, Birkir Gunnarsson <birkir.gunnarsson@deque.com>
- CC: Shane McCarron <shane@spec-ops.io>, Michael Cooper <cooper@w3.org>, Richard Schwerdtfeger <richschwer@gmail.com>, Fred Esch <fesch@us.ibm.com>, ARIA <public-aria@w3.org>
> -----Original Message----- > From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] > Also, I looked at the DOM that the three browsers produce, and there are two > sibling links. That is, the nesting in lost going from the source markup to the > internal DOM. [Jason] What happens if you write: <a href="http://www.example.org/somewhere.html">outer link <a href="http://www.example.org/elsewhere.html">inner link</a> outer again</a> The right solution would be three links, with the third referring to the same destination as the first. I'm struggling to think of good use cases for this nested link functionality though. There could be better ways of achieving whatever the SVG working group participants have in mind for it. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Thursday, 23 June 2016 16:31:52 UTC