Value set previously unspecificed when using back. #52

New Issue

Open

opened 2025-04-03 17:43:23 +02:00 by lash · 2 comments

lash commented

2025-04-03 17:43:23 +02:00

Owner

Set name, family name for first time, then chose "back" on gender. Returned to "family name" which showed "unspecified"

[I] vm:runner.go:402 input match        input=31, next=edit_profile
[I] render:page.go:234 found sink       sym=edit_profile, sink=reset_allow_update
My profile
1: Edit name
2: Edit family name
3: Edit gender
4: Edit year of birth
5: Edit location
6: Edit offerings
7: View profile
0: Back
1
[I] engine:db.go:524 new VM execution with input        input=31
[I] vm:runner.go:402 input match        input=31, next=edit_first_name
[I] render:page.go:234 found sink       sym=edit_first_name, sink=get_current_profile_info
Current name: Not Provided
Enter your first names:
0: Back
Name Schmame
[I] engine:db.go:524 new VM execution with input        input=4e616d65205363686d616d65
[I] vm:runner.go:276 catch!     flag=32, sym=edit_family_name, target=edit_family_name, mode=false
[I] render:page.go:234 found sink       sym=edit_family_name, sink=get_current_profile_info
Current family name: Not Provided
Enter family name:
0: Back
Lame
[I] engine:db.go:524 new VM execution with input        input=4c616d65
[I] vm:runner.go:276 catch!     flag=34, sym=select_gender, target=select_gender, mode=false
[I] render:page.go:234 found sink       sym=select_gender, sink=get_current_profile_info
Current gender: Not Provided
Select gender: 
1: Male
2: Female
3: Unspecified
0: Back
0
[I] engine:db.go:524 new VM execution with input        input=30
[I] vm:runner.go:402 input match        input=30, next=_
[I] render:page.go:234 found sink       sym=edit_family_name, sink=get_current_profile_info
Current family name: Not Provided
Enter family name:
0: Back

Set name, family name for first time, then chose "back" on gender. Returned to "family name" which showed "unspecified" ``` [I] vm:runner.go:402 input match input=31, next=edit_profile [I] render:page.go:234 found sink sym=edit_profile, sink=reset_allow_update My profile 1: Edit name 2: Edit family name 3: Edit gender 4: Edit year of birth 5: Edit location 6: Edit offerings 7: View profile 0: Back 1 [I] engine:db.go:524 new VM execution with input input=31 [I] vm:runner.go:402 input match input=31, next=edit_first_name [I] render:page.go:234 found sink sym=edit_first_name, sink=get_current_profile_info Current name: Not Provided Enter your first names: 0: Back Name Schmame [I] engine:db.go:524 new VM execution with input input=4e616d65205363686d616d65 [I] vm:runner.go:276 catch! flag=32, sym=edit_family_name, target=edit_family_name, mode=false [I] render:page.go:234 found sink sym=edit_family_name, sink=get_current_profile_info Current family name: Not Provided Enter family name: 0: Back Lame [I] engine:db.go:524 new VM execution with input input=4c616d65 [I] vm:runner.go:276 catch! flag=34, sym=select_gender, target=select_gender, mode=false [I] render:page.go:234 found sink sym=select_gender, sink=get_current_profile_info Current gender: Not Provided Select gender: 1: Male 2: Female 3: Unspecified 0: Back 0 [I] engine:db.go:524 new VM execution with input input=30 [I] vm:runner.go:402 input match input=30, next=_ [I] render:page.go:234 found sink sym=edit_family_name, sink=get_current_profile_info Current family name: Not Provided Enter family name: 0: Back ```

lash added the

Kind/Bug

Priority

Low

labels 2025-04-03 17:43:34 +02:00

carlos commented

2025-04-04 09:45:11 +02:00

Member

The design flow for this one is that when users first enter their profile information, the changes aren't immediately visible in the Menu(UI) until they confirm with their PIN.The entered profile item is stored in a temporary array in the background as the user fills the profile items.Only after successful PIN verification does the system save and display the updated profile information.

lash commented

2025-04-04 12:58:13 +02:00

Author

Owner

From UX perspective this is confusing. I suggest this should be kept as an issue and solved at some point as a cosmetic bug. Either that or the back-button should go (but that makes it very complicated with the other flow, I assume)