You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Desired behavior:
A user should be able to set a storypin start and end time in composer. The desired behavior is that the pin shows up at start time and disappears at end time.
Current problem:
The actual "pin" aspect of the StoryPin is respecting the start and end time, but the pop-up does not (when set to "show content automatically). It remains visible after the end time has passed, and even remains going into the next chapter if the story has multiple chapters.
In this screenshot (showing https://mapstory.org/story/23751) a StoryPin with start time 859 and ending in 1190 is there. Content starts showing automatically at 859 and remains. At 1190 the dot for the pin disappears as expected, but the pop up remains.
And it remains even if the story is advanced to Chapter 2.
Example uses Chrome Version 55.0.2883.95 (64-bit).
The text was updated successfully, but these errors were encountered:
cross checked with Darin and Rey on Feb 6.
Desired behavior:
A user should be able to set a storypin start and end time in composer. The desired behavior is that the pin shows up at start time and disappears at end time.
Current problem:
The actual "pin" aspect of the StoryPin is respecting the start and end time, but the pop-up does not (when set to "show content automatically). It remains visible after the end time has passed, and even remains going into the next chapter if the story has multiple chapters.
In this screenshot (showing https://mapstory.org/story/23751) a StoryPin with start time 859 and ending in 1190 is there. Content starts showing automatically at 859 and remains. At 1190 the dot for the pin disappears as expected, but the pop up remains.
And it remains even if the story is advanced to Chapter 2.
Example uses Chrome Version 55.0.2883.95 (64-bit).
The text was updated successfully, but these errors were encountered: