Skip to content

Conversation

@Aryakoste
Copy link

References

Add references/links to any related issues or PRs. These may include:

Description

Added eye icon in password input field of login which toggles.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

@AndreaBarbasso
Copy link
Contributor

@Aryakoste, I feel this is the straightest approach to add some way to show the password, but it does not handle the edge cases mentioned in the linked issue:

Some browsers, such as Edge, already include this functionality natively. Therefore, we should look for a solution that is not in conflict with any (existing or future) native implementation from browsers.

Furthermore, I think that our customization should never be seen on mobile devices, since mobile browsers handle the password show/hide buttons natively.

@Aryakoste
Copy link
Author

@AndreaBarbasso Will make the mobile device change. I had added the Microsoft edge edge case. But was confused that if i should keep native eye icon of Microsoft edge or should I show our newly added icon. Currently it shows newly added icon. So should I show native in Microsoft edge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add an "eye" icon to show the password in the login field

2 participants