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
Maybe we should support a replace mode for hashes.
I've been creating/using HTML5 based slide decks for years with DZSlides, reveal and bespoke. They all modify the current URL hash. It has pros and cons. It's a great feature to :
Share a link pointing to a specific slide
Keep the state if you refresh
But I feel like it's polluting my browser tab history. If I navigate to a slide deck via a link and then pass through slides, it becomes very hard to go back to the origin website.
It's the same with HTML5 slide decks embedded in iframes for presenter console purposes or embedding on classic websites. The history of the iframe messes up with the main window's history.
I propose that this plugin provides a replace on/off switch. On each slide navigation, the current history/state would be replaced (and not added). This would allow to keep all pros and drop the annoying parts.
WDYT?
The text was updated successfully, but these errors were encountered:
Maybe we should support a replace mode for hashes.
I've been creating/using HTML5 based slide decks for years with DZSlides, reveal and bespoke. They all modify the current URL hash. It has pros and cons. It's a great feature to :
But I feel like it's polluting my browser tab history. If I navigate to a slide deck via a link and then pass through slides, it becomes very hard to go back to the origin website.
It's the same with HTML5 slide decks embedded in iframes for presenter console purposes or embedding on classic websites. The history of the iframe messes up with the main window's history.
I propose that this plugin provides a replace on/off switch. On each slide navigation, the current history/state would be replaced (and not added). This would allow to keep all pros and drop the annoying parts.
WDYT?
The text was updated successfully, but these errors were encountered: