<button> instead of <input>

Feature Requests
, , ,
1

It will be a good practice to use modern <button type="submit"></button> html semantics instead of <input type="submit"/> in all frontend forms.

The main reason that WP themes will have more control to customize <button> elements via CSS. It’s possible add inner HTML content (<span>, <strong> or even <img>), and make use of :after and :before pseudo-elements to achieve complex rendering while <input> only accepts a text value attribute.

At the moment Gravity buttons are presented by <input type="submit">, this is really outdated in 2020.

Just check how it was in WooCommerce plugin https://github.com/woocommerce/woocommerce/issues/17254

2

Hello @myph - thank you for the suggestion. I just checked the 2.5 beta release and it’s still an input there, not a button. If you would like to suggest that for inclusion in the future, I recommend adding that to our product roadmap. Click the blue :heavy_plus_sign: in the lower left on this page to add a note for our product team:

https://www.gravityforms.com/gravity-forms-roadmap/

Thank you.

3

Not to be a negative but what about all of us who have configured our CSS using Input.
Changing it to Button may break parts of my site.

Please give us some warning of a change like this. Thank you.

4

Great point Clive. Any breaking change like that will definitely be communicated before it is released. Thanks for bringing that up.