PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Custom CSS address- state dropdown

  1. I'm having difficulty customizing the CSS for a few advanced fields. Specifically, I'm trying to edit the field in the Address group in this form:
    http://www.prodentite.com/wordpress/business-listing/
    This field id is input_1_10.4. I can't figure out the exact css string.

    Thanks in advance.

    Posted 13 years ago on Thursday August 11, 2011 | Permalink
  2. input_1_10.4 is the State drop down on that form in the Address Field. Drop downs have limitations to what you can do to them with styles. Can you describe what exactly you are trying to do and we would be glad to assist you with how to do it.

    Posted 13 years ago on Thursday August 11, 2011 | Permalink
  3. There are a few dynamic field/element id's that contain a "." (dot) in the name that may cause problems when trying to target these directly. The browser thinks the dot is preceding a new class name. That's something we're going back and updating for a future version. You can still target the element just fine for CSS manipulation based on the parent element ID. An example is below.

    [css]
    body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_complex span#input_1_10_4_container select {
    	color:red
    }

    screenshot: http://bit.ly/qepfBz

    Like Carl mentioned, cross-browser styling options for select elements is limited so some properties you try to apply may not work the same if at all in all the browsers.

    Posted 13 years ago on Friday August 12, 2011 | Permalink
  4. Just a quick follow up. I can't replicate the issue with the dot in the ID in the latest version of the plugin. I thought we had already implemented the fix for the issue so I checked and the id output is correct (without the dot).

    You may want to make sure you're using the latest version of the plugin if you're not already. If so, you may have some kind of a plugin conflict that's causing the issue. I'm not sure.

    Either way, the previous CSS snippet should work just fine and the form functionality isn't affected.

    Posted 13 years ago on Friday August 12, 2011 | Permalink