noHtml5Validate should be true by default

[alexose]

Prerequisites

• I have read the documentation;
• In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.
• Ideally, I'm providing a sample JSFiddle or a shared playground link demonstrating the issue.

Description

The default HTML5 validation makes for a confusing UX. For end users, the styling and behavior is inconsistent with the rest of the library (see n1k0's comment here). For developers who are new to react-jsonschema-form, it makes for a puzzling situation when you try to customize how errors are displayed.

Steps to Reproduce

In Chrome:

1. Create a react-jsonschema-form with a single required field
2. Submit the form
3. Observe the 'Please fill out this field' box that appears.

Expected behavior

react-jsonschema-form should have displayed its normal error handling.

Actual behavior

The default html5 form validation overrode the normal error handling.

Version

1.2.1

You can usually get this information in your package.json or in the file URL if you're using the unpkg one.

[epicfaace]

That's a good point. I'm wondering whether it's worth it to introduce this change at this point, since it really might cause some backwards-incompatible behavior and it's not too hard to work around it right now. What do you think @glasserc @edi9999 @LucianBuzzo ?

[edi9999]

I think like you, it is a good idea but since it is backwards incompatible, it should be done in v2 only

[LucianBuzzo]

@edi9999 @epicfaace This interaction is pretty horrible, especially for checkbox/boolean fields. It's definitely a breaking change though, so it should coincide with a major version bump of the npm package.

[sbusch]

+1 for disabling html5 validation by default in V2

I wonder if there's a legitimate need for HTML5 validation? If no, the noHtml5Validate prop and DOM attributes related to HTML5 form validation could be removed completely.

[glasserc]

I would be OK with disabling HTML5 validation in V2.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you.