This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
Remove password strength "control" UI #6564
Milestone
Comments
shane-tomlinson
modified the milestones:
FxA-152: Improve password strength,
FxA-0: quality
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 31, 2018
DesignF is no longer considered experimental, it's the default. Because experiments are not enabled by default in functional tests, the functional tests aren't testing reality. The pw-strength UI is not displayed in the functional tests unless the magic query params `&forceExperiment=passwordStrength&passwordExperimentGroup=designF` are added to the URL. Note, password strength experiment metrics will no longer be sent to Amplitude. blocks #6572 blocks #6573 fixes #6564 fixes #6400
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 31, 2018
DesignF is no longer considered experimental, it's the default. Because experiments are not enabled by default in functional tests, the functional tests aren't testing reality. The pw-strength UI is not displayed in the functional tests unless the magic query params `&forceExperiment=passwordStrength&passwordExperimentGroup=designF` are added to the URL. Note, password strength experiment metrics will no longer be sent to Amplitude. blocks #6572 blocks #6573 fixes #6564 fixes #6400
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 31, 2018
DesignF is no longer considered experimental, it's the default. Because experiments are not enabled by default in functional tests, the functional tests aren't testing reality. The pw-strength UI is not displayed in the functional tests unless the magic query params `&forceExperiment=passwordStrength&passwordExperimentGroup=designF` are added to the URL. Note, password strength experiment metrics will no longer be sent to Amplitude. blocks #6572 blocks #6573 fixes #6564 fixes #6400
ghost
removed
the
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Follow on from #6563.
Now that we have decided
designFis the winner, we should rip out the originalcontrolUI and code.The text was updated successfully, but these errors were encountered: