- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 9 Mar 2012 15:14:31 +1100
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, Steve Faulkner <faulkner.steve@gmail.com>, W3C WAI-XTECH <wai-xtech@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Michael Smith <mike@w3.org>, Janina Sajka <janina@rednote.net>, Judy Brewer <jbrewer@w3.org>
On Fri, Mar 9, 2012 at 12:49 PM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote: > Laura Carlson, Thu, 8 Mar 2012 12:06:52 -0600: > > First off: Steve yesterday confirmed that Internet Explorer's longdesc > implementation is plain wrong: It treats the URL as text string. Thus > it implements it precisely the way the WHATWG blog once ridiculed the > @longdesc usage for. See this bug: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=16268 If that is indeed the case, then all those people that have put hyperlinks into the @longdesc attribute have ended up with non-usable longdesc values in IE. @longdesc is therefore not usable for the purposes that we intend it to be used for, since it is not implemented compatibly across browsers. This to me is a very strong argument to move on to a new attribute so we can start on a clean slate for all relevant elements with well defined implementation details. Silvia.
Received on Friday, 9 March 2012 04:15:20 UTC