- From: <bugzilla@jessica.w3.org>
- Date: Fri, 12 Apr 2013 16:35:58 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21678
Bug ID: 21678
Summary: i18n-ISSUE-251: Invalid content in longdesc
Classification: Unclassified
Product: HTML WG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML Image Description Extension
Assignee: chaals@yandex-team.ru
Reporter: www-international@w3.org
QA Contact: public-html-bugzilla@w3.org
CC: public-html-admin@w3.org
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
needs to pave the cowpath and 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.)
(Sent on behalf of the i18n WG after discussion.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 12 April 2013 16:36:03 UTC