- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Aug 2011 06:50:26 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13546 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-14 06:50:26 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: It would make no sense to allow 'display' as the cues have their own custom display logic. Similarly position/top/left/bottom/right/height/width make no sense as the cues themselves give their dimensions and position. 'overflow' makes no sense since 'auto' and 'scroll' would be meaningless and 'visible' would defeat the whole point of some of the positioning logic. I don't see the use case for 'clip'. 'cursor' seems pointless since they're not interactive. 'z-index' might maybe make sense, but why would you intentionally overlay cues and then layer them out of order? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Sunday, 14 August 2011 06:50:28 UTC