41–45 of 45 posts
Earlier quoted context omitted.
In a native app, such modal would be pushed on the activity stack (on Android; I assume iOS has a similar pattern). It would essentially be a native equivalent of a new page. Modern web developers are, for some reason, more afraid of having multiple pages than they are of black death.
iOS does not push modals onto the navigation stack by default.
What use case would this ever have?
It seems so basic but it’s not straight forward at all to implement in a consistent way across browsers. After trying for a while myself, and not wanting to sink days into it, I’ve given up on finding the perfect solution for now. Going to try the 4th step here, but I believe there’s always a new modal bug waiting to be discovered.
Earlier quoted context omitted.
iOS does not push modals onto the navigation stack by default.
To be fair, iOS doesn't have a universal 'back' button, so you wouldn't reach for it to exit a modal anyway.
What use case would this ever have?
It’s basically a way to have stack navigation on the web, so you can keep the context behind the content it spawned. This is used all the time in native apps, so why not on web? It seems so basic but it’s not straight forward at all to implement in a consistent way across browsers. After trying for a while myself, and not wanting to sink days into it, I’ve given up on finding the perfect solution for now. Going to tr…
I wish this full-screen modal feature would disappear. I've lost track on the number of times I pressed back to close a modal on mobile because I thought it was a new page. Please make it clear that a dialog is a dialog.