Separate dialogs from popovers #961
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#961
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We should separate these usecase:
popover (former modal; popover is the better naming, also allows better distinction from 'model') is used for pages, basically an overlay with a UIs.
popovers usually have a url
dialog: asking the user a question. e.g. delete.
Not sure what to do with modals that had an url but would then loose it. But this also isn't consequent right now: some delete modals have a url others don't.
Popovers should not be stacked (although we might have some exceptions).
Dialogs might be stacked, but this is also discouraged. Better would be to create a user flow where this is not needed.
See also:
#816 (comment)
I like the idea.
That sounds like it should be more consistent.
Did you check which modals have a url and which don't? My guess is all modals which are accessible from the menu directly have one while the ones from a detail page don't.
I didn't check, but that might be!
Either way still not sure which way to go here: I like that there is a direct url for e.g. editing stuff. For deleting it doesn't make so much sense, since you shouldn't be able to navigate back to a delete dialog after you pressed delete.
Because of #1037
I started implementing dialogs based on https://headlessui.dev/vue/dialog but with a promise interface.
Still iterating on that idea.
@konrad: what do you think in general?
If I understood the docs from headless ui correctly, using their dialog component would add the focus trap (that's currently not working)?
In general, I think we could move forward with it.
Yes they implement a lot of heavy to implement accessability stuff in there.
I started with this already, but still in an early phase.
I realized that the dialogs should probably be implemented in a way that you cann them via a function that returns a promise.
Does that make sense?
To remember for later: https://github.com/rlemaigre/vue3-promise-dialog