Because:
- AccountCustomerManager.createAccountCustomer included updateAt as a
parameter even though it wasn't used.
This commit:
- Remove updateAt from createAccountCustomer and update related files.
Closes #
Because:
* We have a new password reset flow that uses confirmation codes instead of link
This commit:
* Remove backbone resetPassword playwright page object model (POM), no longer in use
* Move all reset password tests out of react-conversion folder, and into new resetPassword folder with subfolders for resetPasswordWithLink and resetPasswordWithCode
* Mark the functional tests for reset password with link for deletion with ticket number
* Add new tests updated for reset password with code flow in resetPasswordWithCode folder
* Fix bug with password strength bubble not displayed due to discontinued onFocus metric
Closes #FXA-9612
Because:
* Form submission should be disabled when there was an error on submit
* Re-enable submit after the code is changed
* We want to prevent the user from accidentally hitting the verification limit by submitting the same wrong code too many times
* We do not want the submit button to be disabled if the error is caused by a resend code error
This commit:
* Update the conditions where the submit button in FormVerify code component is disabled
* Remove the aria-label on submit button that was reading the code
* Separate the resend code error state from code verification error state
* Clear all banners before code verification and code resend to make way for new messages
Closes #FXA-9724
Because:
- During development it could be useful to start only parts of the stack
needed for development on specific domains.
This commit:
- Provides additional stack startup options to only start specific parts
of the stack, by using nx projects and tags.
Closes #FXA-9771
Because:
* We want to incorporate the fxa-crypto-relier library into the Firefox
Accounts codebase and deprecated its webextension functionality.
This commit:
* Adds the fxa-crypto-relier library to the Firefox Accounts codebase.
Closes FXA-9741
Because:
* We are emitting this event for successful signup, but not for successful third party auth new account signup
This commit:
* Adds the event
closes FXA-9752
Because:
* We want to track metrics for reset password flow and measure impact of new design
This commit:
* Set up new front-end glean metrics for reset password with code (password_reset_email_confirmation_view, password_reset_email_confirmation_submit, password_reset_email_confirmation_resend_code, password_reset_email_confirmation_signin, password_reset_email_confirmation_different_account) and two new additional new events for existing reset password pages (password_reset_recovery_key_cannot_find, password_reset_create_new_recovery_key_message_click)
* Add Glean pings for theses events in front-end pages
Closes #FXA-9529
Because:
- Prompt none redirect keeps /authentication/* in session history
resulting in awkward behavior when the user uses the back button.
This commit:
- Updates redirect logic to use `replace()`, to replacing the current
resource with the provided redirect URI.
Closes #FXA-9707
Because:
* the `--split-by=timings` default type `file` and alternative type `name` are unsupported for the playwright junit xml file
This commit:
* adds the `--split-by=classname` option
Closes #FXA-9720
Because:
- after migrating to fxa-settings, the backend reg_complete pings no
longer have an oauth client id or service value
This commit:
- sends a metrics context on sign up so that the service value is
cached along with the metrics context
- stop sending a metrics context on verify sign up code so that the
previously cached metrics context is used
Because:
* 'Unexpected error' is displayed when throttling occurs during a password reset
* The consistent fix is to use an already existing handling function
This commit:
* Uses an existing 'getHandledError' function to handle the error, which already differentiates between GQL errors and auth-server errors, which was the crux of the problem
* Moves functions that can be used throughout the app out from the Signin dir and auth-errors file (which also handles oauth errors) to a new file in libs/
fixes FXA-9737