In https://en.wikivoyage.org/wiki/Florence#Q191739 clicking on the blue boxed number 1, the map is correctly opened. Temporary the URL shown in the browser turn into https://en.wikivoyage.org/wiki/Florence#/maplink/9 but if ESC is pressed, the map disappear and return the URL turn back to https://en.wikivoyage.org/wiki/Florence
In https://it.wikivoyage.org/wiki/Firenze#Basilica_di_Santa_Maria_Novella clicking on the blue boxed number 1 instead of having the same behaviour, since today it generates the following error:
Uncaught DOMException: Blocked a frame with origin "https://it.wikivoyage.org" from accessing a cross-origin frame. at Object.OO.ui.Element.static.getDocument (https://it.wikivoyage.org/w/load.php?lang=it&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets%7Cjquery.ui&skin=vector&version=2p8ww:164:64) at Object.OO.ui.Element.static.getDimensions (https://it.wikivoyage.org/w/load.php?lang=it&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets%7Cjquery.ui&skin=vector&version=2p8ww:166:174) at MapDialog.OO.ui.Window.getSize (<anonymous>:29:519) at OoUiWindowManager.OO.ui.WindowManager.updateWindowSize (<anonymous>:25:312) at MapDialog.OO.ui.Window.updateSize (<anonymous>:31:763) at <anonymous>:33:636 at mightThrow (https://it.wikivoyage.org/w/load.php?lang=it&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets%7Cjquery.ui&skin=vector&version=2p8ww:49:149) at process (https://it.wikivoyage.org/w/load.php?lang=it&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets%7Cjquery.ui&skin=vector&version=2p8ww:49:808)
The HTML generated looks the same. Apparently the only two differences are:
- on the href
it:voy: href="https://it.wikivoyage.org/wiki/Firenze#/maplink/5"
en:voy: href="#/maplink/9"
most likely this is not relevant to the current behaviour but is something that can be uniformed
- on the class="geo"
en:voy: the hidden span block is generated server side
it:voy: the same is generated by the local template
Regardless the bug, these two aspects should be uniformed.
I used Chrome latest version. I've tested it after a user highlighted the problem in our local "lounge". He used both Safari and Chrome.