maptalks / maptalks/maptalks.js
Markers are not clickable on some Android phones
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4.5k
- Forks
- 511
- Avg merge
- 3d 58m
- Merged PRs (30d)
- 1
Description
I'm getting complains that marker popups don't open in Chrome on some Android phones. Affected maps:
- https://maptalks.org/examples/en/ui-control/ui-geo-infownd/ (official example)
- https://joric.github.io/maps/fallout-london/ (canvas version)
- https://joric.github.io/stalker/ (opengl version)
The affected browser is supposedly Chrome on Galaxy S22. I can't really check that. It works on my Xiaomi and Pixel phones. I tried adding logging via Eruda, added an extra openInfoWindow call, but it looks like the browser doesn't generate click events for the markers. I don't know maybe there are options that must be set or it's a Galaxy-only browser bug, not sure. My phones work. It's not the only case, I've had the same complaints from the android users before. Official examples also seem affected.
- Maybe it's the way I replace InfoWindow content in maptalks. Updated both maps, added an extra openInfoWindow. Also added some logging, does console add 'clicked' record on click now? Also can you close and open info window in the example here? https://maptalks.org/examples/en/ui-control/ui-geo-infownd/
- Nope, none of that is working..
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the official ui-geo-infownd example and reproduce the marker interaction in Chrome on an affected Galaxy S22, comparing it with the Xiaomi or Pixel behavior. Check whether marker clicks and info-window opening occur in the official example, the canvas map, and the WebGL map; done means marker popups open reliably on the affected Android device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100