-
Notifications
You must be signed in to change notification settings - Fork 203
GitHub username text is unclear #2791
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
Comments
@martinthomson thanks for the comment. Currently the flow is this (and sure can be improved as we are testing for the last couple of weeks this new feature aka github username)
The difference in between 2 and 3 is that people do not have to give webcompat so many permissions. See #655 This was the intent to cater for people who are uncomfortable with this big list of permissions. Also the GitHub username field is only visible if the user is not already logged in. The flow you are proposing is not exactly doing the same thing (if I understood). |
Thanks @karlcow, I'm not suggesting a change in process. I think that these are the right reporting flows, given the constraints as I understand them. All I'm doing here is trying to suggest using different words on the form to better communicate what is going to happen. |
This relates to #2762 too. |
We changed things a bit. The username is not hotlinked anymore. And the wording has been tweaked. Let's see if that improves thing a bit. Thanks for the feedback. |
Maybe remove the "publicly visible" bit from the github username field. It is redundant now (and thus still a little confusing). |
This text...
... combined with the two buttons "Report Anonymously" and "Report via GitHub" is confusing.
The without logging in might be read to imply that you are not going to be required to authorize an application or log in even if you choose the "Report via GitHub" option. That is not the case.
Also, "This will be publicly visible" might be read to imply that none of the other information will be. It's all public info (#2690).
My suggestion:
With the latter only becoming accessible when a GitHub username is entered (I think that this is already the case, but I didn't double-check).
The text was updated successfully, but these errors were encountered: