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
If i see a certain cool pic. that i want to share somewhere, i currently can't.
We need the parameters of current-image, date- and time- range in the url.
The text was updated successfully, but these errors were encountered:
If state is in the URL, should the App be navigable via history?
(eg. browser-back to go to previous image)
Probably not.
So maybe only provide a URL with the current state via a Share-Button, and not have it in the url by default?
If so, what happens if that URL with state-info is loaded?
(after a user opens that shared URL)
Probably the app would only read it at startup, then ignore it?
Might be confusing later for a user, if the state is different then what's seen in the Browsers URL-bar.
So maybe after reading, the App should rewrite the URL, removing state-info?
I guess there are best practices for these Questions to be found online...
If i see a certain cool pic. that i want to share somewhere, i currently can't.
We need the parameters of current-image, date- and time- range in the url.
The text was updated successfully, but these errors were encountered: