- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 May 2011 20:03:05 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12309
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |FIXED
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-06 20:03:05 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: Accepted
Change Description: see diff given below
Rationale: Well, ok, but seriously, who's putting sensitive information into a
font that's so sensitive that the very presence of a character gives something
away? It's not like non-font files are going to accidentally be interpreted as
fonts, either, this information has to have actually been put in a font
somehow.
--
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, 6 May 2011 20:03:12 UTC