Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Navigation Hash Widget Error in Google Chrome Browser #47

Open
drusexton opened this issue Jul 7, 2017 · 2 comments
Open

Navigation Hash Widget Error in Google Chrome Browser #47

drusexton opened this issue Jul 7, 2017 · 2 comments

Comments

@drusexton
Copy link

@BrianBunker

When using Google Chrome to access an application that implements the Navigation Hash widget there is an error when you attempt to open a new tab in the browser window and access another URL that has a Navigation hash reference. I have tested this issue in other browsers, but have only been able to recreate it in Google Chrome. The error occurs almost every single time, but on occasion will not.

In #740 I list the following steps to recreate this issue:

  1. Open the application in Google Chrome using the following public URL.
  2. Open a new tab in the same browser window.
  3. Paste the public URL from step 1 into the address bar and hit enter.
  4. There are no errors in the browser console.

The map should zoom to the same extent in the second browser tab as it does in the first browser tab. Rather what you will see is that in the second browser tab the latitude and longitude has been ignored, and that the map is instead zoomed to the extent of the map center using the specified zoom from the Navigation Hash widget.

Any help to resolve this issue would be excellent!

@BrianBunker
Copy link
Owner

Just an observation: the nav hash does not update on pan/zoom in second tab since there seems to be a race condition with the map panning/zooming events that happen on application load. If you manually update the nav hash in the url, the app will pan to the correct location.

@gregoryj98
Copy link

I set the initial extent of the map (on load) to that of the coordinates in the URL and that seemed to fix things up...but probably not the correct way to fix the problem - I am not super familiar with dojo stuff.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants