News for hackers. Stuff that matters.
Re:<dialog>: The Dialog Element by stevage on Friday December 06, 2024 @05:00PM (#42344987)
> no-one wants an unmovable popup or modal-dialog that completely obscures the user's view of an underlying document

Eh, I beg to differ. Lots of use cases for that kind of dialog, for saving, confirming changes, etc etc.

Re:<dialog>: The Dialog Element by DaiPlusPlus on Friday December 06, 2024 @05:29PM (#42345256)
> confirming changes

...how can I confirm a set of changes if the popup is blocking my view of said changes?

Re:<dialog>: The Dialog Element by _0x168 on Friday December 06, 2024 @05:51PM (#42345440)
The popup can summarize the changes. For instance, "are you sure you want to delete X?"
Re:<dialog>: The Dialog Element by stevage on Friday December 06, 2024 @06:00PM (#42345503)
And yet, that pattern has worked just fine for decades.
Re:<dialog>: The Dialog Element by DaiPlusPlus on Friday December 06, 2024 @06:53PM (#42345901)
On a Windows or macOS desktop, the OS-provided MessageBox() can be freely moved around the screen - but that's not how in-web-page modals tend to work.
Re:<dialog>: The Dialog Element by stevage on Friday December 06, 2024 @08:03PM (#42346296)
I don't find I have the problem you describe, because at worst you can generally abort the save or whatever and verify then redo it.

The one that bugs me is online order forms that don't give you all your critical details like dates, and exactly what you are paying for, on one screen where you finally commit.

Re:<dialog>: The Dialog Element by rat9988 on Saturday December 07, 2024 @02:54AM (#42348047)
Then don't confirm them if you aren't sure you wanted to confirm. The dialog is here to alert that you did click on confirm and it seems to me you weren't ready yet, so it did its job.
Re:<dialog>: The Dialog Element by zelphirkalt on Saturday December 07, 2024 @05:01AM (#42348609)
Famous example of how badly this works is Jira. Want to look something up in another ticket? Bad luck! You need to close that ticket, then open the other one, then memorize or copy the info you need, then close that ticket, then open the original one again. At that point you are better off circumventing the whole shit UI and clone the browser tab. Which ultimately leads to having a dozen browser tabs open that one needs to cleanup later. Add to that the general incredible sluggishness of Jira, and the massive amount of things loaded when you load any of its pages, and you have a recipe for the disaster that thing is.