Please do not remove support for the CSS Ready Class gf_invisible. We use it in numerous situations (many forms and several sites) for fields already configured so that their visibility setting is hidden. “Why on earth would you do such a thing?” I hear you asking. “If you already set the field’s visibility to hidden, then you should not also need to add gf_invisible.”
But we often do, and here’s why: we have tons of Gravity Flow workflows in which a hidden field’s functionality is necessary for conditional logic. This means that the field, although hidden, must appear among those displayed for the relevant step (e.g., user input or approval). In such cases, the “hidden” field is shown to the user, but the user has no business seeing it since it’s purely there for functionality. Adding gf_invisible to a field set to hidden in its visibility settings has been the perfect solution for us. Please, please keep it. Thanks!
When the CSS Ready Classes are deprecated in Gravity Forms, you can carry the class forward in your own projects by adding the following to your theme stylesheet or Custom CSS:
Yes, thanks, I realize that, but it is quite a massive chore to update hundreds of fields on hundreds of forms using the CSS Ready Classes. Many of us who have used Gravity Forms for 10+ years have a huge number of updates to make in preparation for this change. I really hope that you will find a way to support your customers who have been following your documentation for years and using CSS Ready Classes until these warnings started appearing. Perhaps you would consider creating a plugin or snippet that would automate the migration. Thank you for considering the idea.
Gravity Forms 3.1 won’t be released for at least a year, 3.0 is still in development, so you have plenty of time to plan and implement the required changes.