- From: <bugzilla@jessica.w3.org>
- Date: Fri, 11 Nov 2011 01:14:13 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14709
John Daggett <jdaggett@mozilla.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #31 from John Daggett <jdaggett@mozilla.com> 2011-11-11 01:14:11 UTC ---
> How OpenType behaves is up to OpenType.
>
> Within HTML, the intent is that so long as you use only conforming
> values, the behaviour is clear, and if you use non-conforming
> values, HTML UAs will not treat them as value values and non-HTML
> contexts built on top of HTML, e.g. CSS, will operate as defined by
> those contexts. This is because I do not think we want to require
> that browsers validate every language tag before trying to match CSS
> selectors, e.g.
This bug isn't about OpenType, it's about how user agents deal with
language subtags when it's necessary to interface with other API's
that use language tags of one form or another. In these situations a
mapping of some form is needed, so the question here is what should
tags that are not valid BCP47 tags map to? A null mapping? Or should
invalid values simply be passed through?
Given the language highlighted in comment 11, the spec can be read
either way. The lang attribute specifies a valid BCP47 tag so the
mapping should be a null mapping. But it's unknown so it should be
passed through.
No one commenting on this bug is arguing that validation should occur
when matching CSS selectors.
--
Configure bugmail: http://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 Friday, 11 November 2011 01:14:19 UTC