Mtg on Nostr: Hey Lana How are you So just to confirm I understand the issue: You are referring to ...
Hey Lana
How are you
So just to confirm I understand the issue:
You are referring to the case where:
1- You go to some profile settings page (e.g. Basic Info page)
2- You fill some data in some fields
3- You navigate to some other profile page (e.g. Roles & Skills page) WITHOUT clicking "Save Changes"
4- You make some changes there
5- You go back to the Basic Info page
6- The info you entered without saving isn't there anymore
Is that right??
If so, then yes, this behaviour could be improved.
There are 2 options that we could go with, each with its pros & cons.
1- Treat all the profile pages as a single form but with multiple tabs. So the "Save changes" button would save the changes on all the different tabs, not just the current one.
Pros:
\- This way, the user won't lose any info he enters at all
Cons:
\- The user might forget that he made changes to some page that he is not on now.
\- Reviewing changes before saving will require the user to go back to each page & scan what changes he made.
\- If there is an error with some field on some page after submitting, it won't be easy to display this error if the user is on a different page.
\- The user might expect that if he move away from a page without saving, his form fields should go back to the original values.
I personally think this approach is only suitable for the cases where the forms are small & only consists of a couple of fields each.
But in our case, the forms are bigger, and more pages will likely be added in the future.
2- If the user made changes on one page, and he tries to navigate to a different page before saving, we show a prompt saying something like:
"You have some unsaved changes on this page, are you sure you want to move away without saving them??"
Pros:
\- Keeps the data, errors, & loading of each page contained within itself
\- Easier for the user to review his changes before saving
\- If the user wants to remove his changes, he can navigate away from the page & confirm to "Not save"
Cons:
\- The browser prompts dialog is not very pretty honestly (but maybe there is a way to customize it later)
I think this approach is more suited for the profile settings case, (it can be seen in websites like Gmail profile settings for example).
And we actually used to use this approach previously, but we disabled it at one point due to some changes in the page, and didn't add it back.
So maybe we should add it back now.
What are your thoughts??
How are you
So just to confirm I understand the issue:
You are referring to the case where:
1- You go to some profile settings page (e.g. Basic Info page)
2- You fill some data in some fields
3- You navigate to some other profile page (e.g. Roles & Skills page) WITHOUT clicking "Save Changes"
4- You make some changes there
5- You go back to the Basic Info page
6- The info you entered without saving isn't there anymore
Is that right??
If so, then yes, this behaviour could be improved.
There are 2 options that we could go with, each with its pros & cons.
1- Treat all the profile pages as a single form but with multiple tabs. So the "Save changes" button would save the changes on all the different tabs, not just the current one.
Pros:
\- This way, the user won't lose any info he enters at all
Cons:
\- The user might forget that he made changes to some page that he is not on now.
\- Reviewing changes before saving will require the user to go back to each page & scan what changes he made.
\- If there is an error with some field on some page after submitting, it won't be easy to display this error if the user is on a different page.
\- The user might expect that if he move away from a page without saving, his form fields should go back to the original values.
I personally think this approach is only suitable for the cases where the forms are small & only consists of a couple of fields each.
But in our case, the forms are bigger, and more pages will likely be added in the future.
2- If the user made changes on one page, and he tries to navigate to a different page before saving, we show a prompt saying something like:
"You have some unsaved changes on this page, are you sure you want to move away without saving them??"
Pros:
\- Keeps the data, errors, & loading of each page contained within itself
\- Easier for the user to review his changes before saving
\- If the user wants to remove his changes, he can navigate away from the page & confirm to "Not save"
Cons:
\- The browser prompts dialog is not very pretty honestly (but maybe there is a way to customize it later)
I think this approach is more suited for the profile settings case, (it can be seen in websites like Gmail profile settings for example).
And we actually used to use this approach previously, but we disabled it at one point due to some changes in the page, and didn't add it back.
So maybe we should add it back now.
What are your thoughts??