Closed
Bug 481389
Opened 16 years ago
Closed 8 years ago
Make sure only valid language attribute values are exposed
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: MarcoZ, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: access, Whiteboard: [bcp47])
Right now, our code basically exposes what either the markup or the headers tell us. So if the author writes "dumdoolittle" as a lang attribute value, we'll just expose that without checking for validity. We should expose a value conforming to RFC 4646 (http://www.ietf.org/rfc/rfc4646.txt) and RFC 4647 http://www.ietf.org/rfc/rfc4647.txt) and parse out/unify any invalid or bloated values.
Comment 1•16 years ago
|
||
The doc http://www.w3.org/International/articles/language-tags/ and our implementation of IAccessible2 might be helpful as well.
Comment 2•8 years ago
|
||
Closing as part of a batch cleanup of old untouched bugs. This bug hasn't been touched for at least 2000 days.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•