Pass the expected account email to the WP.com login webpage #23766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
This PR is built on top of #23749 and requires the changes in D165346-code.
When re-authenticating or signing in to a Jetpack site, we expected a specific WP.com account. We already have checks in place to throw an error if users sign in with an unexpected WP.com account. However, from UX perspective, it'd be better to pre-fill the username/email text field on the login page with the expected WP.com account email. That's what this PR does.
Test Instructions
Use Jetpack login as an example.
The username/email text field in the login web page should be prepopulated with the email addresses of the account used in step 1.
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR submission checklist:
RELEASE-NOTES.txt
if necessary.Testing checklist: