- From: <bugzilla@jessica.w3.org>
- Date: Sun, 26 Sep 2010 00:47:26 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10546
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |NEEDSINFO
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-26 00:47:25 ---
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: Did Not Understand Request
Change Description: no spec change
Rationale:
I don't know, is there any good reason to restrict it as such?
Is there any precedent in the HTML spec's rendering section to restrict a CSS
property on an element in this way?
--
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 Sunday, 26 September 2010 00:47:27 UTC