mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1182] Add back button to account setup process #789
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#789
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @pinpontitit on GitHub (May 25, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1182
Describe the feature you'd like to request
Hi
I could use a "Go back" button in "newAccount.vue" process.
For example in step 1, I choose Google, so it takes me to step 2.
But then I regret and would prefer use Nextcloud.
To come back to step 1 there's no "Go back" button (I don't know how you would say in english)
I always have to close the tab and open a new newAccount.vue page.
If you are already at step 4 and want to come back to step 3, its such a pain in the ass to close the tab and start everything from scratch than just clicking Go back button.
Thanks
Describe the solution you'd like
..
Describe alternatives you've considered
..
@marcelklehr commented on GitHub (May 26, 2022):
Meta comment: Please open one issue per proposal so it's easier to keep track of what is being proposed.
@github-actions[bot] commented on GitHub (Jul 5, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.