Consider options for form validation support

[NickBosworth]

Form validation using components vs native html elements can be problematic.

for example some libraries require the exposure of the internal html element which is not consistently available, plus this adds extra complexity and code which defeats one of the major purposes of the library.

Given the majority of form scenarios require client side form validation, at least in a static / spa scenario - would it be ideal to either provide a solution as a part of flowbite-svelte or provide some form of extensibility to make a solution such as svelte-use-form perform as it does natively? as opinionated as this may be?

Just interested in starting the conversation. Its a problem I have consistently faced across component libraries and the authors opinion is usually that it is not the libraries place to be concerned with it. However, by the nature of the design of many component libraries they make validation implementation difficult, requiring "hacks" etc to meet parity with a native html experience.