Comment on Brut: A New Web Framework for RubyparentComments−MortyWaves1yIs there a reason you literally simulate a click event on the form instead of calling submit() on it?−Mystery-Machine1y`requestSubmit()`*https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormEle...−rorylaitila1yYeah, it's escaping me at the moment all of the reasons, but calling .submit() on a form element doesn't exactly have all of the behaviors as calling .click() on a button element in a form, particularly multiple buttons in a form.−hapidjus1yAre you perhaps using the button name/value for something? Havent tested but i suspect that submit() does not pass that right?−rorylaitila1yYep that's one reason. I make heavy use of that.
Comments
Is there a reason you literally simulate a click event on the form instead of calling submit() on it?
`requestSubmit()`*
https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormEle...
Yeah, it's escaping me at the moment all of the reasons, but calling .submit() on a form element doesn't exactly have all of the behaviors as calling .click() on a button element in a form, particularly multiple buttons in a form.
Are you perhaps using the button name/value for something? Havent tested but i suspect that submit() does not pass that right?
Yep that's one reason. I make heavy use of that.