The template en:OSM Location map, which used to use a 'Graph:' display-engine before that was turned off, is now back through a combination of <mapframe> and inline css. It is now working well in standard browsers, has minor postioning issues in browser mobile mode, and gets badly mangled within the Android app. The problem is that the template relies on mapframe with a matching overlay <div>, which positions the various graphical and text elements onto the basemap. However the app re-sizes and centers the mapframe basemap, and then appears to use the left edge and the original scale for the overlays, so that they have the wrong origin and the wrong scale. Narrow maps that need little scaling are affected less, but even a 350px map such as that at https://en.wikipedia.org/wiki/Isca_Augusta en:Isca Augusta ends up all over the place, and the map at https://en.wikipedia.org/wiki/Leicester#Geography is not a pretty site. There are currently 5,600 pages with OSM Location maps, so a solution is clearly desirable. If, for example, there was a way of stopping the <mapframe> from re-sizing, and ensuring both items started at the same edge, that might be one option, or (sounds tricky to me) ensuring all the css is scaled to the same as basemap. Any suggestions would be useful. Thanks.
Topic on Talk:Wikimedia Apps/Flow
Hello @RobinLeicester,
Could you please share some screenshots with us at any of our support email addresses:
android-support@wikimedia.org
ios-support@wikimedia.org
I have forwarded your inquiry to our engineers and will attach these screenshots to a Phabricator ticket. and send you the link after receiving the screenshots.
Thank you!