- From: TAMURA, Kent <notifications@github.com>
- Date: Wed, 26 Dec 2018 02:08:51 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 26 December 2018 10:09:12 UTC
@caridy > we will wait until it is implemented behind a flag The latest Google Chrome Dev and Canary have this feature including form validation. > (multiple form elements competing for one name with the corresponding coordination of their respective states) I don't catch this part. Would you elaborate on this, or show some examples please? > form reset protocol I think existing ```'reset'``` event is enough. A form-associated custom element listens to the event on the owner form element, and posts a task in the event handler, then the task checks ```defaultPrevented``` and resets the element's state if it's false. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/187#issuecomment-449943524
Received on Wednesday, 26 December 2018 10:09:12 UTC