Compatibility with Display Suite

Did some quick testing and the behavior (although it seems like CF doesn't seem to be that stable yet) was the same with or without DS layout.
Pretty sure this is a CF issue, but I'll leave it open until someone can give some steps to reproduce.

Tagging as important before making an RC because of potential API changes - we'll be investigating this next week.

untagging as release blocker

I'm not sure that this is a DS issue but what i've experienced is that code fields and dynamic fields, do not show up as dependent or dependee fields in the conditional fields UI. Which makes sense because conditional fields requires the EDIT CONTEXT SETTINGS of the form to be filled out in order to show VIEW CONTEXT SETTINGS. And DS fields don't exactly show up in the node edit form.

Unfortunately it's a shame it works this way because it would be very useful to be able to conditionally display DS fields. Maybe there's a way to plug in DS fields into the CF UI and make this work? PM me i can probably get some funds together for this to happen...

I've been thinking a bit more on this and another option would be to create a module which depends on http://drupal.org/project/field_formatter_settings
I'm going to investigate this week.

I'm turning this into a feature request.

I just uploaded Field formatter settings (note in extreme alpha status) - see http://drupal.org/project/ffc - has support for field api and ds fields.

I'm not going to support this (or at least write myself), everything is focused on ffc.

This article suggests the problem may be with the Conditional Fields module: Conditional Fields and Display Suite

Just confirming the "problem" here. Per that article from comment 8: The dependee field needs to be visible in the Display Suite layout. If it's not there is assumes the condition has not been met.

My work around for now was to add the dependee field and then hide it with CSS.