← Back to context Comment by andrewflnr 3 months ago > giving buttons to abilityMight want to fix that. :) 3 comments andrewflnr Reply tln 3 months ago I haven't seen the proposal, but buttons can already set the form method (and action, and more). So I guess the "Button HTTP Requests" will just save the need to nest one tag? <form><button type="submit" formaction="/session" formmethod="DELETE"></form> <form action="/session" method="DELETE"><button type="submit"></form> andrewflnr 3 months ago To be clear, I was referring to the minor typo. jjcm 3 months ago This proposal also includes the ability to update a target DOM element with the response from that delete action.
tln 3 months ago I haven't seen the proposal, but buttons can already set the form method (and action, and more). So I guess the "Button HTTP Requests" will just save the need to nest one tag? <form><button type="submit" formaction="/session" formmethod="DELETE"></form> <form action="/session" method="DELETE"><button type="submit"></form> andrewflnr 3 months ago To be clear, I was referring to the minor typo. jjcm 3 months ago This proposal also includes the ability to update a target DOM element with the response from that delete action.
jjcm 3 months ago This proposal also includes the ability to update a target DOM element with the response from that delete action.
I haven't seen the proposal, but buttons can already set the form method (and action, and more). So I guess the "Button HTTP Requests" will just save the need to nest one tag?
To be clear, I was referring to the minor typo.
This proposal also includes the ability to update a target DOM element with the response from that delete action.