Skip to content
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

add audit to check if paste is allowed in password inputs #2366

Merged
merged 9 commits into from
Jun 5, 2017

Conversation

robin-drexler
Copy link
Contributor

@robin-drexler robin-drexler commented May 25, 2017

Adresses #2345

todo

  • add/format violation output
  • proper copy (help text, description)
  • tests

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is awesome stuff thanks @robin-drexler! 🎉

when you start on adding output, we can follow the accessibility audits model of showing the outerHTML of the element (can take a look at the axe-audit.js in audits/accessibility for the output object format, feel free to ignore the proprietary "path" part for now :) )

for tests, a smoke test in the dobetterweb tester would be perfect too 👌

feel free to reach out to us for any help if you get stuck and thanks for the contribution!

@paulirish
Copy link
Member

nice nice! this is on point so far. well done. :)

@robin-drexler
Copy link
Contributor Author

Output currently looks like this:

lighthouse_report

Is this any good?

Could anybody help me with the failing build? I can't seem to figure out why it's breaking. Everything looks pretty good, but it still exits with exit code 1. Thanks in advance! :)

@robin-drexler
Copy link
Contributor Author

I just didn't look thoroughly enough, sorry. There was a linting issue which should now be resolved.

@robin-drexler
Copy link
Contributor Author

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@robin-drexler
Copy link
Contributor Author

Should I also create a doc page like https://developers.google.com/web/tools/lighthouse/audits/geolocation-on-load ?

If that's the case, can somebody point me to the respective repo? :)

@wardpeet
Copy link
Collaborator

@@ -133,7 +134,8 @@ module.exports = {
"dobetterweb/notification-on-start",
"dobetterweb/script-blocking-first-paint",
"dobetterweb/uses-http2",
"dobetterweb/uses-passive-event-listeners"
"dobetterweb/uses-passive-event-listeners",
"dobetterweb/password-inputs-can-be-pasted-into"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit, all these audits are arranged alphabetical, maybe order them here too

@@ -26,6 +26,7 @@ module.exports = {
"dobetterweb/response-compression",
"dobetterweb/tags-blocking-first-paint",
"dobetterweb/websql",
"dobetterweb/password-inputs-with-prevented-paste",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit, all these audits are arranged alphabetical, maybe order them here too

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

@robin-drexler
Copy link
Contributor Author

I'd like to finish this during the weekend but probably could use some help with copywriting and docs and some hints on what else might need to be done.

Could anyone chime in? :)

@robin-drexler robin-drexler changed the title [WIP] add audit to check if paste is allowed in password inputs add audit to check if paste is allowed in password inputs Jun 3, 2017
Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Robin, this is so good.

Everything here is in its right place and I got nothing but praise for this PR.

@paulirish paulirish merged commit 68044ba into GoogleChrome:master Jun 5, 2017
@paulirish
Copy link
Member

Huge. Thank you!

🥇 🥇 🥇

@robin-drexler
Copy link
Contributor Author

Fantastic, can't wait to see it in a release. :D
Thanks for all your help @wardpeet @paulirish :) 🎉

@paulirish
Copy link
Member

all good! sorry for not being timely in our replies.

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.

5 participants