- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 23 Feb 2010 06:54:49 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8754 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-02-23 06:54:48 --- 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: This doesn't seem to be in scope for HTML. This problem exists with any element in CSS, not just <iframe>s. If you have a <p> element with a given width and height in pixels, and the font-size is changed without the author's intent, then an 'overflow' value other than 'scroll' or 'auto' will similarly cause problems. Fixing this just for <iframe> isn't a thorough solution. In general, UAs that only allow changing the font size are generally not going to work. The recommended way of providing zooming is to zoom the pixel size, not the font size, and this handles this case fine. It also happens to be what all UAs do these days. -- 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 Tuesday, 23 February 2010 06:54:57 UTC