- From: Daniel Freedman <dfreedm@google.com>
- Date: Tue, 19 Mar 2013 10:21:58 -0700
- To: Константинов Сергей <twirl@yandex-team.ru>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Received on Tuesday, 19 March 2013 17:22:49 UTC
Example 1 is what `touch-action: pan-x` is for. System controlled scrolling in the X axis, with PointerEvents generated in the Y axis. Example 2, you would place `touch-action: none` on the map and do nothing for the info window, which will pinch-zoom as platform dictated. In both examples, the css is static, and therefore you don't have to call preventDefault on any event. On Tue, Mar 19, 2013 at 2:24 AM, Константинов Сергей <twirl@yandex-team.ru>wrote: > > I've to disagree with you on this. CSS *is* a perfectly valid way to > configure the browser behavior. > > When you need to alter browser behavoir statically - maybe. > > Example 1: Safari two-finger scroll. Our task is to prevent browser > behavior (page scroll) on vertical scroll and not to prevent browser > behavior (history back/forward) on horizontal scroll. > Example 2: we have a map and info window on it. Our task is to prevent > browser behavior (page zoom) in favor of map zooming when the fingers are > on map; and we want not to prevent the same behavior (page zoom) when > fingers are on the info window. Both map and info window are rendered on > canvas. > > What we have to do? Dynamically change CSS properties? That's ridiculous. > In Safari we can just call preventDefault on touchmove event. > > >
Received on Tuesday, 19 March 2013 17:22:49 UTC