Known bugs/issues with Shortlist Story Map??

138
1
Jump to solution
10-31-2017 03:46 PM
kmsmikrud
Occasional Contributor III

Hi,

I was hoping to find out if a couple of issues are know bugs in the Shortlist Story Map. It was pointed out yesterday that when a user clicks on a site photo instead maybe zooming in to that location on the map or possibly another photo the application goes to the next site location photo? This does not seem like a desired action for the user, can you tell me if someone is working on this or why it was designed this way?

Also some users were having trouble with their back arrow within the site location photo box. For instance if they did click on the photo and the photo changed to the new location they then couldn't use the arrow to move back to the original site. I'm not sure if this is a browser update issue or what. It was working for some folks and not others.

Here's a link to the story map.

Thanks for your help,
Kathy

0 Kudos
1 Solution

Accepted Solutions
RupertEssinger
Frequent Contributor II

Hi Kathy

Those aren't bugs with Shortlist: that is how it is designed

Your Shortlist looks great by the way.

When you are looking at the info panel for a place (the panel with the photo, < > X arrows, and description under the photo:

  • Clicking the photo is simply a shortcut for clicking > to move on to the next place in the sequence of places, the same as in Story Map Tour. We did this to make it faster to browse through the places in a Shortlist without having to hit the quite small > button each time

  • When you click the < or > buttons, it will go back or advance through the sequence of places. So the < button isn't a back button like in a web browser. I think what you are reporting here is the following: If you have zoomed in on a particular area, and the Shortlist is one that uses the default behavior where only those places that fall inside the current area shown in the map are listed in the tabs, then the < and > buttons will cycle through the places in that area, not all the places in your Shortlist. In this way if you zoom in on one area, it is easy to browse the places in that area.

    If you'd prefer that clicking < or > lets your users browse through all the places, whether or not they are in the current extent shown on the map, you could go to the Settings in the Shortlist browser and switch the behaviour of your Shortlist so that the tabs always show all the places in your Shortlist, irrespective of the current map extent.


Rupert

View solution in original post

0 Kudos
1 Reply
RupertEssinger
Frequent Contributor II

Hi Kathy

Those aren't bugs with Shortlist: that is how it is designed

Your Shortlist looks great by the way.

When you are looking at the info panel for a place (the panel with the photo, < > X arrows, and description under the photo:

  • Clicking the photo is simply a shortcut for clicking > to move on to the next place in the sequence of places, the same as in Story Map Tour. We did this to make it faster to browse through the places in a Shortlist without having to hit the quite small > button each time

  • When you click the < or > buttons, it will go back or advance through the sequence of places. So the < button isn't a back button like in a web browser. I think what you are reporting here is the following: If you have zoomed in on a particular area, and the Shortlist is one that uses the default behavior where only those places that fall inside the current area shown in the map are listed in the tabs, then the < and > buttons will cycle through the places in that area, not all the places in your Shortlist. In this way if you zoom in on one area, it is easy to browse the places in that area.

    If you'd prefer that clicking < or > lets your users browse through all the places, whether or not they are in the current extent shown on the map, you could go to the Settings in the Shortlist browser and switch the behaviour of your Shortlist so that the tabs always show all the places in your Shortlist, irrespective of the current map extent.


Rupert

View solution in original post

0 Kudos