You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
db v132 added new columns and tables to represent the FAForever terms of service.
The next step is to check on each login, if a member already accepted the latest ToS.
If the ToS in the user data is not the latest, right after entering username/password the user must be shown a screen with the latest ToS and button to accept. If the ToS is accepted, store this information in the login data of that user and proceed with the OAuth consent screen.
The text was updated successfully, but these errors were encountered:
What should be the title of the dialog in English, I will add i18n for it
Is the style for the Accept/Decline buttons ok, is the text of the buttons ok (i18n will be added if not exists)
2.1. (UX question) Should there be a decline button at all ?
Currently if user clicks Decline, nothing happens, just the dialog gets closed, what should be the behavior ?
I would do the same things we do when the user declines the consent screen. Cancel the login flow in the hydra service. On top of that I would show a non-closable dialog (e.g. registration view) that login is not possible as long as the ToS are not accepted. Later on we might need to add a link on how to delete the account.
Also that kind of brings me to the point that the account deletion process must work outside the login flow, otherwise you cannot delete your account without accepting the ToS.
db v132 added new columns and tables to represent the FAForever terms of service.
The next step is to check on each login, if a member already accepted the latest ToS.
If the ToS in the user data is not the latest, right after entering username/password the user must be shown a screen with the latest ToS and button to accept. If the ToS is accepted, store this information in the login data of that user and proceed with the OAuth consent screen.
The text was updated successfully, but these errors were encountered: