Hi Boris - That's awesome, thank you.
On Fri, Nov 3, 2017 at 6:23 PM Boris Zbarsky wrote:
> On 10/31/17 10:56 AM, Regis Kuckaertz wrote:
> > Indeed I find your idea more appealing and semantically clearer.
>
> OK, good. Since it's not just me, I filed
> https://github.com/whatwg/html/issues/319
On 10/31/17 10:56 AM, Regis Kuckaertz wrote:
Indeed I find your idea more appealing and semantically clearer.
OK, good. Since it's not just me, I filed
https://github.com/whatwg/html/issues/3195 on this.
-Boris
Thanks for your question. Phrased like that, it becomes clear to me that I
did not think enough about how the value would be computed in the case of a
set of buttons. There is no "checkedness" in buttons, not that I know of.
Indeed I find your idea more appealing and semantically clearer. When I
w
On 10/31/17 6:23 AM, Regis Kuckaertz wrote:
formElement.onsubmit = (evt) => {
evt.preventDefault();
const button = evt.target.elements.namedItem('action');
const value = button.value
If this returned buttons, which button would you expect it to return in
various situations and why?
Hello,
The other day I came across the following behaviour and would like to ask
your opinion on the matter. It is not uncommon to find forms such as:
Add to
favourites
Duplicate
Delete
When a user presses one of these buttons, the UA picks the corresponding
value and streamlines it i