It does not work in IE11.

[sjcoala]

Current Behavior
It does not work in IE11.

Expected behavior
I expect it to work in Chrome, Safari, and IE11.

How to reproduce
Sample data such as zika.json are available. (dir : /home/user1/test/auspice/zika.json)

1. Create conda virtual environment. (with python 3.8) conda create --name auspicetest -c conda-forge python=3.8
2. Install nodejs 12 conda install --name auspicetest -c conda-forge nodejs=12
3. Unzip the downloaded auspice source zip file. ( /home/user1/miniconda3/envs/auspicetest/auspice )
4. conda activate auspicetest
5. Install nextstrain-cli python -m pip install nextstrain-cli
6. Install auspice cd /home/user1/miniconda3/envs/auspicetest/auspice npm install --global .
7. Build auspice auspice build
8. View auspice nextstrain view --allow-remote-access /home/user1/test/auspice/
9. Open it Safari, Chrome and IE11. It does not work in IE11. F12 developer mode in IE11 and look at the console log. An error such as object DOMException appears.

Possible solution
(optional)

Your environment: if browsing Nextstrain online

• Operating system:
• Browser:

Your environment: if running Nextstrain locally

• Operating system: CentOs7
• Browser: Safari, Chrome and IE11
• Version : Python 3.8.8, nodejs - v12.19.0, nextstrain_cli 3.0.3, auspice 2.24.1

Additional context

1. Open the https://nextstrain.org/zika site in F12 developer mode in IE11 and look at the console log. An error such as object DOMException appears. In my case, it is the same phenomenon.

2. Map invisible phenomenon when not localhost (ex: http://123.123.123.123:4000/testdata/) ==> Change the access-token value used in https://auspice.us in the src/util/globals.js file and build auspice. You can see the map well.

[emmahodcroft]

Thanks @sjcoala

I haven't tested with locally running auspice but can confirm that loading up nextstrain.org/ncov/global doesn't work on IE11:

[trvrb]

Looks like IE11 still has ~1% market share (https://caniuse.com/usage-table). I can't test this on my computer, but if it's a simple fix it would be nice to do so. These have previously been simple JavaScript swaps. I'll leave this issue open but flag as low priority.