- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Feb 2011 08:27:18 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12044
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |LATER
--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-16 08:27:18 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: Partially Accepted
Change Description: none yet
Rationale: I don't usually like this kind of feature, because it relies on
authors making good judgements and that has historically not been a successful
strategy for Web browser vendors. However, in this particular case the issue
isn't really about optimisation (as it is for 'image-rendering'), it's about a
very concrete desire to actually see the pixels blown up. This is something we
probably _should_ address.
I've marked this "LATER", so we don't lose track of it. However, now is not a
great time to add this, because before adding more new features we should first
let the browsers catch up to what we've already specced.
--
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 Wednesday, 16 February 2011 08:27:19 UTC