- From: <bugzilla@jessica.w3.org>
- Date: Fri, 29 Jul 2011 19:45:16 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13453
Maciej Stachowiak <mjs@apple.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjs@apple.com
--- Comment #1 from Maciej Stachowiak <mjs@apple.com> 2011-07-29 19:45:16 UTC ---
I think the correct approach here is:
- Scaling from CSS width/height (regardless of source) and the img width and
height attributes is applied before interpreting the image map coordinates.
- Scaling from CSS transforms or UA-controlled zoom features (such as a
UI-level full-page zoom feature, or something like iOS punch-to-zoom) are
applied after interpreting the image map coordinates.
The reason for applying UA features after interpreting the image map is that
sites have no way to account for this. The reason for applying CSS transforms
after interpreting the image map is that there is no legacy behavior to
preserve in this case, and CSS transforms can also impose translation, rotation
and skew which should definitely *not* be applied.
--
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 Friday, 29 July 2011 19:45:17 UTC