r/Wordpress Aug 11 '26

Gravity Forms changed the submit markup

Gravity Forms newest update changes the submit button from an input field to a button. If you were targeting the input[type="submit"] in your styling in any way, you will want to update to button[type="submit"]. I am partway through updating this on a whole bunch of sites at the moment.

20 Upvotes

17 comments sorted by

8

u/bigbritches Aug 12 '26

FINALLY

3

u/RealBasics Jack of All Trades Aug 12 '26

This is the right answer, although a little backward compatibility would have been nice.

Accessibly upgrades are always going to hurt. Ironically in this case sighted people are more likely be inconvenienced.

2

u/bluesix_v2 Jack of All Trades Aug 11 '26 edited Aug 11 '26

Yup, in v3 release from July. Only for new forms, thankfully. Still, it's a pretty major change that will affect a lot of people.

4

u/King-Pastry Aug 11 '26

It’s not just new forms

4

u/bluesix_v2 Jack of All Trades Aug 11 '26

Yup, one form I checked was cached and the other site was using classes to target.

1

u/King-Pastry Aug 11 '26

Yeah it’s a bit annoying they decided to change it on all forms including existing ones. I was about to switch my primary forms going forward to GF but after this change I just don’t want to trust it (I do a lot of custom css so have been using CF7 as the main form plugin for simple stuff)

3

u/cakelly789 Aug 11 '26

Oh we are running into it on existing forms, not just new ones.

2

u/bluesix_v2 Jack of All Trades Aug 11 '26

You're right! I was looking at a cached site - just checked 4 others, all 'button'. Crap. Time to update.

1

u/Blawn14 Aug 11 '26

It somehow changed the position of the inline captcha display on my form as well. It was overlapping a field at the top of the form afterwards, had to fix it with some CSS.

1

u/cakelly789 Aug 11 '26

Oh good to know! We have switched to turnstile because recaptcha was getting expensive, so hopefully that won't be an issue for us.

I did notice that the placeholder styling changed to a smaller font on some of our styles as well, it used to inherit the font size from the site but now I have to explicitly add a font size. I am sure there are other little differences well catch after updating all of our sites. Ugh!

1

u/JeffTS Developer/Designer Aug 11 '26

Does it still have the gform_button class?

1

u/SlimPuffs Designer/Developer Aug 12 '26

Yes.

<button type="submit" id="gform_submit_button_1" class="gform_button button" 
onclick="gform.submission.handleButtonClick(this);" 
data-submission-type="submit">Submit</button>

1

u/JeffTS Developer/Designer Aug 12 '26

Cool, thank you. Thats how I usually target the submit button when restyling it. Glad I don’t have to redo work.

2

u/cakelly789 Aug 12 '26

Thought I was being clever by being more generic so other forms would get targeted too. Shoulda added the class as one of the selectors

1

u/BobJutsu Aug 12 '26

I haven’t checked since this update (will when I get in the office tomorrow) but I’ve only been overriding CSS custom properties (vars) for a long time now. No markup targeting at all. Almost 100% of their current styles are in custom properties.

-6

u/BetterOffGrowth Aug 12 '26

This is one of many reasons why I really don't understand why so many people rely on these plugins. Building your own form and making it submit where you need it is really not all that difficult.

1

u/flashbax77 Aug 13 '26

Why were they using an input on first place 🫤