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

Error message is missing from the "Type of bug" section #2725

Closed
cipriansv opened this issue Dec 6, 2018 · 5 comments
Closed

Error message is missing from the "Type of bug" section #2725

cipriansv opened this issue Dec 6, 2018 · 5 comments

Comments

@cipriansv
Copy link
Collaborator

cipriansv commented Dec 6, 2018

Steps to reproduce:

  1. Navigate to: https://staging.webcompat.com/issues/new
  2. Start filling the required fields.
  3. Skip to select a radio button from the "Type of bug" section.
  4. Fill in the rest of the fields.
  5. Click the "Report" button.

Expected Behavior:
"A type of bug must be selected" error message must be displayed above/under the "Type of bug" section.

Actual Behavior:
Nothing happens. No error message is displayed.

Notes:

  1. Screenshot attached.
  2. The issue is also reproducible if the "Is this information correct" section is empty.
    "A browser version/Operating system is needed" error message must be displayed above/below the section's text field.

Watchers:
@softvision-oana-arbuzov
@softvision-sergiulogigan
@cipriansv

sv;

image

@karlcow
Copy link
Member

karlcow commented Apr 25, 2019

To solve this, there is a need for an event listener on Report buttons, when they are not active, and double check that the Type of bug has been selected.

In fact, we should probably display the error messages on all fields only when someone is trying to click the report button and the fields are incomplete.

  • Create tests for checking if error messages are displayed once we click the report button
  • Remove the current behavior where the error message is displayed when the field has not been completed
  • Replace the asterisk by (mandatory) in black
  • Display the error message in red only when someone try to click on Report and mandatory fields are empty

@ksy36
Copy link
Contributor

ksy36 commented May 21, 2019

@karlcow Should fields in "Is this information correct" section become mandatory as well?
If this is the case we'll probably need to add labels for those fields (Browser version and Operating system).

@karlcow
Copy link
Member

karlcow commented May 21, 2019

About

Should fields in "Is this information correct" section become mandatory as well?

So far it has not been that much of an issue, the information sent by the browser is mostly correct. It is rare that people delete it AND more important probably many people have no idea what would be the correct way to enter these. I even wonder if they should be hidden in a kind of expert mode for people who needs to modify them because they know what they are doing.

Maybe AB testing could help us to figure this out #2873

ksy36 added a commit that referenced this issue May 27, 2019
…er submit button is clicked. Replaced asterisk with (mandatory)
@ksy36
Copy link
Contributor

ksy36 commented May 27, 2019

Regarding Remove the current behavior where the error message is displayed when the field has not been completed:

There are certain checks being performed on the Site URL field, for example, to determine whether the string is a valid url. Here are the test cases explaining the behavior.

So, when an invalid string has been typed in the URL field and we switch to another field, the error should still show up, correct @karlcow ? Since for a user it's good to see the error right away, before clicking on the submit button.

@karlcow
Copy link
Member

karlcow commented May 27, 2019

So, when an invalid string has been typed in the URL field and we switch to another field, the error should still show up, correct @karlcow ? Since for a user it's good to see the error right away, before clicking on the submit button.

yes.
On the other hand, the error should not show anymore if one types something wrong, then delete and switches to another field.

ksy36 added a commit that referenced this issue May 30, 2019
ksy36 added a commit that referenced this issue May 30, 2019
ksy36 added a commit that referenced this issue May 31, 2019
ksy36 added a commit that referenced this issue May 31, 2019
…coming from the report site issue extension
ksy36 added a commit that referenced this issue Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants