Constraints should not be implemented in the Form component IMO.

So a solution could be to use the normalizer to add aRegex constraint when the option is true.

So a solution could be to use the normalizer to add a Regex constraint when the option is true.

But then we should not require the Validator component for such option, add do it in theColorType directly using apreg_match in a listener instead.

I agree, this could simply be part of theColorType. For consistency with other form types I suggest to add anhtml5 option which renders an HTML5input="type" widget and performs these validation rules.

I took your ideas into consideration. That's kind of out of my initial use case but it's still going to be useful.

which renders an HTML5 input="type" widget

AFAIK, that's already the case.

do it in the ColorType directly using a preg_match in a listener instead.

Should we however add a RegExp constraint (and skip the listener) if the Validator component is there?

Thank you@fancyweb.