ISSUE-251: Invalid content in longdesc ⓒ

Invalid content in longdesc ⓒ

State:
CLOSED
Product:
html-longdesc
Raised by:
Richard Ishida
Opened on:
2013-04-05
Description:
Bug 21678 - i18n-ISSUE-251: Invalid content in longdesc
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21678


Section 3
http://www.w3.org/TR/2013/WD-html-longdesc-20130312/#longdesc


"If a longdesc attribute has invalid content, user agents may make that content available to the user. This is because a common authoring error is to include the text of a description, instead of the URL of a description, as the value of the attribute."


Allowing authors to include the text of a description rather than a URL can lead to significant issues for non-English text.

User agents SHOULD NOT make this information available. Authors SHOULD learn to do it right.

Otherwise:
1. authors may persist in misusing the attribute to the point that someone issues an extension that allows user readable content in the longdesc attribute.

2. user readable content in attributes cannot be marked up for bidirectional text, language, or styling. Nor is it easy to indicate whether such text is intended to be translated or not for machines or translators. It should therefore be avoided where possible. (It's a bad enough situation to still have things like alt and title lying around, let's not make it worse, especially with a feature that encourages long, rich text content.)
Related Actions Items:
No related actions
Related emails:
  1. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2014-08-28)
  2. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-05-09)
  3. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-05-02)
  4. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-05-02)
  5. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-05-01)
  6. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-05-01)
  7. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-04-17)
  8. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-04-16)
  9. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-04-12)
  10. [Bug 21678] i18n-ISSUE-251: Invalid content in longdesc (from bugzilla@jessica.w3.org on 2013-04-12)
  11. I18N-ISSUE-251: Invalid content in longdesc [.prep-html-longdesc] (from sysbot+tracker@w3.org on 2013-04-05)

Related notes:

spec now says that value must be a url, but there's an informative description of a hack that allows a browser to turn a value that's not a valid url into a data: url (suggested by Leif)

Propose we close this issue.

Richard Ishida, 13 Aug 2014, 16:07:06

Closed and comment added to bugzilla to say that we are satisfied with the current spec text.

Richard Ishida, 28 Aug 2014, 11:46:08

Display change log ATOM feed


Addison Phillips <addison@amazon.com>, Chair, Richard Ishida <ishida@w3.org>, Fuqiao Xue <xfq@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $