[OpenLayers-Dev] android browsers, pan and select controls

Richard Duivenvoorde rdmailings at duif.net
Thu Mar 3 15:46:39 EST 2011


christopher.schmidt at nokia.com wrote:
> On Mar 3, 2011, at 8:25 AM, ext Richard Duivenvoorde wrote:
>> 1) opera running/selecting fine as long as the touchnavigation control
>> is not used.
> 
> Opera does not currently have any support for touch events.

I can pan the map on my Android phone, which is nice, actually I do not
care which exact event is used.
But in Opera, selecting the feature dot's is always working.

>> 2) firefox: touchnavigation not working, selection is working
> 
> I'm assuming you mean Firefox on android devices? Firefox does not implement
> any kind of touch events on non-Windows7 Operating Systems, according to
> their documentation.

Yep, we are all talking these three browsers on an Android 2.2 (Desire
HD) phone.
And like Opera: selecting/clicking the features is always working.

>> 3) android browser: selection is working sometimes but behaves strange,
>> touchnavigation is working

In Android browser selecting is unpredictable:
http://83.161.239.58/test/

To make myself more clear :-)

I need the functionality of selecting features in the android browser
(because this (webkit?)browser is used in the webview-control that is
used in PhoneGap. The testing with the other browsers is just to see if
the strange behaviour I see in the android/webkit browser is browser
specific (and it is).

At first I thought there was a relation with the TouchNavigation
control, but after disabling or removing it, the strange selecting
behaviour continues (as if the div's are too small or just missed).

I forgot to mention I used a fresh build from Trunk of today.

Hoping somebody gives me a little clue on where to look/debug to see
what is going wrong.
One observation: when selecting a feature in the android browser, the
full map is 'activated' sometimes.
Another observation: sometimes selecting a feature works, then a couple
of times it is not and apparently after clicking on the canvas and
trying again is works again.

I have to find out/log the exact cascade of events I think to debug this
case. Any idea's are appreciated.
I will try to make a very minimal build nonminimized build also.

Regards,

Richard Duivenvoorde


More information about the Dev mailing list