BRouter-Web on iOS behavior: collection of bugs (e.g. touch input interpretation, show my location)
Opened this issue · 2 comments
I thought there was an issue here adressing some of these frequent hickups when using BRouter-Web on iOS, but I searched all issues and beside some very specific iOS bugs, there is no issue for the most common bugs on iOS, so I thought it's about time to open one.
(Although I somewhat learned to avoid using BRouter-Web on iOS as best as I can and if I have to use it, I try to work around most limitations in ways I figured out by simply a lot of trial & error)
I think it's a major flaw of BRouter-Web that makes this wonderful solution really hard to recommend to any cyclist that uses an iPhone, simply because it just does not provide a good User Experience.
You either plan your tours ahead of time at home on a PC/Mac (which I kinda have to), or you really have to bring a lot of patience with you if you need to plan on the go on your iPhone.. 😅
(Most problems apply to Safari, but also other iOS Browsers like Chrome. I think the reason is that on iOS, basically every Browser App is kinda forced to use the same Webkit Engine by Apple.)
- Using your location simply does not work, no matter how often you approve the iOS prompt to allow your browser to access your location
- If you try to enable "Edit Mode" with the Pen Icon on the Left, you have to long-press, which also triggers text selection of the icons
- When panning / zooming the Map with Edit Mode active, BRouter Web randomly interpretes a Pinch&Zoom gesture as a click and, very annoyingly, then places unwanted Waypoint Markers on to the map. To avoid this, every time I need to zoom / pan the map, I have to try to disable Edit Mode which brings all sorts of other problems with it.
- Every other attempt at disabling Edit Mode or other touch interactions randomly result in BRouter-Web permantly behaving like you have one finger on the screen, so you cannot Zoom / pan anymore in a controlled way. Only solution at that point is to reload the whole page.
- And probably a few more bugs
iOS is buggy since years
an iPhone [...] just does not provide a good User Experience
FTFY (SCNR).
Have you tried complaining to your browser engine vendor (Apple) about this?
buggy since years
100 more inconveniences
Not sure what you are trying to achieve here. Make developers feel even more guilty about their long list of open issues and even less motivated to fix things in their free time? It somewhat distracts from your otherwise well-meaning bug report. It might not have been your intention, but at least as a contributor to BRouter-Web I do not enjoy having to read demands like this on a regular basis.
Regarding the question implied in the title: Apparently the number of BRouter-Web developers owning iOS devices, caring about that platform and at the same time willing to allocate time and energy fixing those issues has been quite low since a while. Your best bet might be to fix things yourself (or hire someone to do it for you) and send patches.
Also note that some of the issues might or might not be fixed by upgrading to a newer version of Leaflet, which itself is currently blocked by lack of resources to fix incompatibilities in unmaintained dependencies (see dd07150). Let us know if you want to help with that.
It somewhat distracts from your otherwise well-meaning bug report. It might not have been your intention [...]
Fixed (or at least tried to, currently still on a multi-day bike trip)
Your best bet might be to fix things yourself [...] and send patches.
I have this in the back of my head since some time. I will have to take tiny steps at best though to get my feet wet and build some confidence / knowledge about the way the project's architecture is set up. Btw this issue was not intended / written to "demand" something, it just tries to collect / list the most common bugs on iOS i frequently have to work around and did not find any issues about.