https://www.w3.org/Bugs/Public/show_bug.cgi?id=23259
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23259
Gary Kacmarcik gary...@google.com changed:
What|Removed |Added
CC|
Hi Travis,
On 12/09/2008 02:15 AM, Travis Leithead wrote:
Pixel scrolling / line scrolling aren't intended purpose. They are describing
the data browser gets from the operating
system.
At least on Windows-OS, this binding of pixel/line scrolling to a wheel event
does not exist. I think
some
larger amount is scrolled.
I thought we already have specified a scroll event for this purpose?
That happens after something on the page has been scrolled. Mouse wheel events
are dispatched
when user uses the wheel (for scrolling, or zooming or whatever the webapps
want to do with wheel
and there isn't always
a good way to convert pixel scroll data to line scroll data.
So to help web apps, better to have separate events.
Note, currently in Mozilla there are separate wheel events for
horizontal and vertical scrolling and events have .axis property.
So
http://dev.w3.org/2006/webapi
Doug Schepers wrote:
And that causes problems like
http://mozilla.pettay.fi/moztests/pixelscrolling.mov
Can you provide some context for what is going on in that video? What
is the problem that illustrates? Does it relate to the scrolling vs.
zooming of the map?
The problem is that