OAuth 2.0-based authentication of users and devices, user profile management, Single Sign-On (SSO) and Identity Federation across multiple administration domains.
What types of changes does your code introduce to the project: Put an x in
the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality
to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.
[ ] I have added tests that prove my fix is effective or that my feature
works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream
modules
Further comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc...
Proposed changes
Change input type to email and inputmode to email. The latter one will show a custom keyboard on mobile devices which directly contains an "@" and a button for the dot. https://css-tricks.com/everything-you-ever-wanted-to-know-about-inputmode/
Types of changes
What types of changes does your code introduce to the project: Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...