Daniel Florey

Also a reportValidity() would be great to be able to validate and show validation messages programmtically.

It would be great if the tags would reflect the "chapters" in the reference documentation. I think that it is more or less common practice to use the tags as...

You can test the "chapters" by pasting the stripe openapi spec into the redoc tool: http://rebilly.github.io/ReDoc/?url=https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec2.yaml This is a great way to get an idea how the API will show...

Running into the same issue. The stripe api definition starts like this: ``` "definitions": { "account": { "properties": { "business_name": { "description": "The publicly visible name of the business.", "type":...

Thanks for the quick fix!

I'm lazy and would prefer B. It would probably be nice to have an option (strict mode or something) that will then turn on Option A

Cross-posting here as this seems to be the right place. When calling `reportValidity()` on a native input field it will display the error message using the built-in UI (e.g. error...

Yes, I could fire an invalid event just like native input elements - once my reportValidation() method would get invoked. But it is never called. I guess once the MWC...

Thanks, will do. Form my understanding after reading the validation API spec `setCustomValidity()` is meant to be used by component users, not component authors and that makes perfect sense to...

As stated above the problem is that there is no way to create a custom element that -adds the value to the formdata on form submission -performs the validation check...