31–40 of 45 posts
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.
In the previous century when web technologies were more primitive, modal dialogs were created in new browser windows. We all remember pop-ups and what a horrid experience that was. Developers (and spammers) abused this behavior so much that browsers now reflexively prevent pages from opening new windows in most cases. I leave almost any site that interrupts me with a full screen modal dialog, especially if it's a pro…
It’s completely reasonable for a product to advertise for a newer version. How else would you know there’s a new version that you might actually decide you want to buy? And you don’t have to buy it.
In the previous century when web technologies were more primitive, modal dialogs were created in new browser windows. We all remember pop-ups and what a horrid experience that was. Developers (and spammers) abused this behavior so much that browsers now reflexively prevent pages from opening new windows in most cases. I leave almost any site that interrupts me with a full screen modal dialog, especially if it's a pro…
Sites do this because 90% of users don’t leave over modal popups and doing it increases engagement in enough cases to warrant keeping it. It’s completely reasonable for a product to advertise for a newer version. How else would you know there’s a new version that you might actually decide you want to buy? And you don’t have to buy it.
No argument from me there. A notice on the splash screen, even a tool tip at start-up would work fine, but it was a full screen advertisement, several minutes after start-up, which stopped playback (!) without warning. These interruptions are what I find completely unacceptable, and I believe they stem from fundamentally misunderstanding what the user is there for, or outright disrespect.
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.
This is interesting, in a native app the modal would close but unintuitively most sites don't push modals to history.
In the previous century when web technologies were more primitive, modal dialogs were created in new browser windows. We all remember pop-ups and what a horrid experience that was. Developers (and spammers) abused this behavior so much that browsers now reflexively prevent pages from opening new windows in most cases. I leave almost any site that interrupts me with a full screen modal dialog, especially if it's a pro…
Sites do this because 90% of users don’t leave over modal popups and doing it increases engagement in enough cases to warrant keeping it. It’s completely reasonable for a product to advertise for a newer version. How else would you know there’s a new version that you might actually decide you want to buy? And you don’t have to buy it.
Advertising's role is chiefly to create demand and manipulate people into buying things, not to inform.
If one is not looking for new versions, then they very likely don't need them.
Earlier quoted context omitted.
Sites do this because 90% of users don’t leave over modal popups and doing it increases engagement in enough cases to warrant keeping it. It’s completely reasonable for a product to advertise for a newer version. How else would you know there’s a new version that you might actually decide you want to buy? And you don’t have to buy it.
> It’s completely reasonable for a product to advertise for a newer version. No argument from me there. A notice on the splash screen, even a tool tip at start-up would work fine, but it was a full screen advertisement, several minutes after start-up, which stopped playback (!) without warning. These interruptions are what I find completely unacceptable, and I believe they stem from fundamentally misunderstanding wha…
Earlier quoted context omitted.
Not exactly "a page", as with a modal you are not messing with the browser history and you expect to keep the exact state of the page underneath the modal
I'm in two minds here - a set of tools/patterns exist for a reason so this is a useful write-up for the difficulties involved with doing modals. On the other hand, it is always a warning indicator when the browser/hardware is fighting against me. In this particular case I feel "modal" is an implementation detail - as long as you don't break the UX contracts (i.e. browser history is left unchanged and page state under…
I feel like the hazard here is that many developers don't know, care about, or care about knowing, the full extent of the UX contract, and as a result implement something that's only halfway there.
My go-to example of this is one of the Java UI toolkit of old, which reimplemented all controls but tried to make them look as if they were native. The end result was a set of controls that kind-of looked like native ones, except they didn't support appropriate context menus and less-known keyboard shortcuts.
What about just removing what you can't see from the DOM entirely, and load it in again when the dialog closes? Wouldn't be too hard with React or Vue. Just make it so either the page content or the modal is loaded.
You can do that, but the visitor's scroll position would be reset, when the modal is closed.
"Full screen modal dialog" is just another way of saying "a page" right? So some HTML and you are done? I am not sure but from the name of the repo I am guessing this is referring to React JavaScript framework which I think is purely "single page application" deal which would explain the limitation of not being able to load a separate page. Shame we are reimplementing the wheel for such trivial and basic use-cases. O…
If this is using React (it's not actually clear from the .md file, the only hint is the parent repo name), then this is very easily solved: replace the page with the modal. The solutions seem to be trying to solve this for a normal HTML page without changing page, which is a harder problem.
> The solutions seem to be trying to solve this for a normal HTML page without changing page, which is a harder problem.
This is a very good point. In an actual spa there is no reason to overlay the modal rather than create a new route
Earlier quoted context omitted.
This is interesting, in a native app the modal would close but unintuitively most sites don't push modals to history.
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.