- From: <bugzilla@jessica.w3.org>
- Date: Wed, 20 Aug 2014 16:29:57 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26611
Evan Wallace <evan.exe@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |evan.exe@gmail.com
--- Comment #4 from Evan Wallace <evan.exe@gmail.com> ---
The intent isn't just to be able to prevent the default zoom behavior, but also
to be able to implement custom zoom behavior. For example, a zoom event in a
map application over the map area wouldn't zoom the entire page but would zoom
the map instead.
As an app developer, zoom events are easiest to use for custom zoom behavior
when the detail value just provides an incremental delta instead of the
absolute zoom level. For example, if a keyboard zoom in/out action is part of
this event, then either a multiplicative delta of *2 or *0.5 or an additive
delta of +1 or -1 (in log space, so the scale is something like *pow(2,
additiveDelta)) would be the most useful.
Providing the absolute zoom level in the event is inconvenient because the
application likely has its own representation of zoom that has nothing to do
with the browser zoom. For example, the scale of the map in a map application
usually changes by 100x during a session. Tying the scale of the map to the
absolute zoom level doesn't make sense.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 20 August 2014 16:30:02 UTC