-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Checkbox with 'required' parameter attribute #1014
Comments
Good point, thanks for reporting this issue! We absolutely failed to see this issue in the fix. Now that you mentioned it, all parameters were recognized as
Let's just say it is not well documented. Bridge maintainers simply had no chance of knowing better. For the sake of simplicity, however, the second point should be implemented before adding more complexity to bridges. That being said, we need to be more clear on the meaning of 'required'. Currently there are at least three interpretations depending on the point of view:
Obviously it doesn't make sense to have a checkbox be That means, checkboxes should simply ignore the |
This should be fixed in master. Please try again. |
That was fast :) Now it works ! Thanks ! |
Since 288d4de, there is an issue with the "Pepper" bridge Family :
Those two checkbox parameters have the attribute required :
hide_local
hide_expired
Since the change, the Bridge card set the two checkbox as required and if not checked, an HTML5 browser will refuse to submit the form for the bridge.
Is the bridge using 'required ' in a false way for checkbox, or the Bridge Card should not use "required" when checkbox are involved ?
The text was updated successfully, but these errors were encountered: