-
Notifications
You must be signed in to change notification settings - Fork 166
LG-9973: Implement new default Sign In page from A/B test results #8542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -321,7 +321,6 @@ session_total_duration_timeout_in_minutes: 720 | |
| ses_configuration_set_name: '' | ||
| set_remember_device_session_expiration: false | ||
| sign_up_mfa_selection_order_testing: '{ "default": 100, "authentication_app_priority": 0, "usability_priority": 0 }' | ||
| sign_in_a_b_testing: '{ "default": 100,"tabbed" :0, "banner": 0 } ' | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 😱 can't believe we had the extra space inside that string there, glad we're removing it
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
😅 Luckily it seemed to tolerate pretty well regardless! |
||
| sp_handoff_bounce_max_seconds: 2 | ||
| show_user_attribute_deprecation_warnings: false | ||
| otp_min_attempts_remaining_warning_count: 3 | ||
|
|
||
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a useful param to keep at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It could be, but my YAGNI hardliner instincts tell me we don't have an immediate use for it detached from the A/B test.
Generally, I do find that we're increasingly wanting to track "clicks" and correlating how a user arrives at a particular place, but maybe that's something we'd want to have some generic support for (e.g. a
referrerbase property on analytics events, or usingClickObserverComponentnow that its implemented withsendBeaconas of @matthinz's improvements in #8496†).† Previously, I would have avoided
ClickObserverComponentfor links which navigate the user away, since you couldn't trust that the analytics would be logged unless adding some async await + spinner button, often more trouble than it was worth.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW I think a
refererproperty on events could be useful (perhaps normalized to just the path, could even leave it nil for links from other hosts if we wanted).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(obviously we'd keep the misspelling from HTTP 😄 )