Re: [w3c/webcomponents] Need callback for form submit data (#187)

@caridy, thank you for the explanation.  As @domenic already wrote, coordination like built-in radio buttons can be implemented without UA's help.  I made an example of radio-button-like custom element; https://jsfiddle.net/int32_t/dep4Lyhj/4/

I found following issues during developing the example:
  - ```setFormValue('', new FormData())``` should submit nothing.  The current Chrome implementation adds ***name***= to the query string.  It was unclear in the proposal document.
  - I assumed UA called the mandatory ```value``` setter to restore page state.  However control's ***value*** and control's ***state*** are separated in built-in input[type=radio] and input[type=checkbox], and their ```value``` setter doesn't change their checkedness state.  We should rename the mandatory setter to something like ```restoreState()```

As for the reset callback, I think it's ok to add it.  I thought form reset is not used nowadays, and no one wanted it.

> I'm still struggling to get the example to work on canary (Version 73.0.3652.0) ...

It should work.  Does https://jsfiddle.net/int32_t/dep4Lyhj/4/ work for you?

> ... the 3rd argument on the define() call, ...

I changed it from ```define()``` flag to static field of the class because the latter works better for class inheritance.

-- 
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-450105076