W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri

From: <bugzilla@jessica.w3.org>
Date: Wed, 25 Jul 2012 11:47:23 +0000
Message-Id: <E1Su03n-0001Q1-W8@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18385

--- Comment #5 from Laura Carlson <laura.lee.carlson@gmail.com> 2012-07-25 11:47:23 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > > It will be feasible after the longdesc is reinstated in HTML5. It is ISSUE-30.
> > > 
> > > That could happen in Last Call 2 and not have to wait for HTML.next.
> > 
> > Reference:
> > http://lists.w3.org/Archives/Public/public-html/2012Apr/0211.html
> 
> I was not aware of this. BTW, the reference states "expanding longdesc to other
> attributes in the HTML5 time frame." It does not specify what those attributes
> are. 
> 
> If this bug is redundant, please close it.

Hi Devarshi,

This bug isn't redundant. If ISSUE-30 [1] is resolved successfully, discussion
of expanding longdesc in Last Call 2 can take place. In the mean time
documenting use cases is useful preparation. Further elaboration on which
elements you feel longdesc would be useful on and why would be appreciated.

Thank you.

[1] http://www.w3.org/html/wg/tracker/issues/30

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 25 July 2012 11:47:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 July 2012 11:47:31 GMT