-
Notifications
You must be signed in to change notification settings - Fork 192
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
Fixes #2725: Bugform validation improvements #2886
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the future, it's kinda nice to read individual commits to understand the changes, rather than a giant one without a lot of context. If you prefer squashing after, that's fine too.
What's the plan for indicating required form elements to the user? It seems like we've removed that here except for the one that says mandatory.
Yeah, sorry :) I had individual commits in v1 branch, but then after we refactored the form here, decided to move these validation changes to v2 branch and base them on the refactored version. So they all landed in one commit.. For the required fields there were 2 more missing |
Actually I've just noticed a small issue, will be fixing it shortly. |
No issue! Just makes it a bit easier to review in chunks. |
…coming from the report site issue extension
Ok the last issue is fixed now. I made it so the errors don't show up on page refresh or when coming from the report site issue extension, so a user will see them only when clicking on submit. @miketaylr could you please review the commit? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome. Thanks!
@karlcow can we push this branch to staging to do a quick sanity check the form still behaves as we expect. It LGTM locally. |
(we can merge now, or wait until we check it out on staging, no strong preference here) |
@ksy36 @miketaylr this branch is deployed on staging. |
Thanks Karl. I'll poke around before merging. |
@ksy36 I think I discovered a bug: https://staging.webcompat.com/issues/1882 STR: open the bug form on staging.webcompat.com/issues/new Expected: the form should not submit I checked the STR on production, and if you delete all the text, we run validation. So this would technically be a regression (probably a super-corner case). Do you want to try to fix here? Or in a follow up bug? |
@miketaylr weird, I'm not able to reproduce - the button becomes slightly grey and disabled once I press |
I'm not 100% sure. But it's pretty edge-casey, so let's merge here and I'll file a follow up if I can reproduce in a new profile. |
r? @miketaylr