- From: <bugzilla@jessica.w3.org>
- Date: Fri, 11 Nov 2011 00:19:14 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14709
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #30 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-11-11 00:19:09 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
http://dev.w3.org/html5/decision-policy/decision-policy.html
Status: Rejected
Change Description: no spec change
Rationale:
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.
I do not think the sentences quoted in comment 11 contradict each other; one
applies to HTML UAs, and the other applies to the input passed to non-HTML
contexts.
--
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 00:19:21 UTC