I’m not sure why you felt it was okay to mark this one as resolved. It’s not very resolved when you have to jam some workaround into the document head, either into a template or register and enqueue it and get it to show up in the right place. Most WP admins aren’t developers.
Maybe you’re comfortable by just blaming themes or other plugins and just letting your user-base figure this out on their own by stumbling on this “solution,” but that’s not the reputation for support I’ve heard from the many people who use CF7. People say it’s fantastic… but this way of handling this issue is a brush-off.
What theme includes form validation scripts that intentionally put validation errors IN the form field and then make it impossible for the message to disappear when you focus on the field again? And, if you use placeholder text, then you have a validation error that won’t go away and placeholder text that won’t go away. I can’t think of a better way to drive prospects or customers or clients to abandon the form. It’s marketing genius!
Pardon the sarcasm, I guess, but there’s too much blaming themes and plugins and the WP core as the solution to everything.
I hope you will officially address this and figure out how to fix it and incorporate the fix in an update that includes the issue in the version update details as a debugged bug, and not just mark the issue “resolved.” That would be good customer support.