Fields set as controlling filters do not hide dependent filters

I've already posted this in http://drupal.org/node/1618444 but that issue has been marked as fixed and the issue explained below deviates a bit from the original issue posted there.

I set up a new sandbox just to play around with this module and found out that it does not hide dependent exposed filters if the controlling filter is a field. For example, say you have a content type called "Vegetable" and it has fields called, "plant type" and "flower color." You make these two fields exposed filters in the view, but you only want the "flower color" filter to show if someone selects certain value(s) in the "plant type" filter. For whatever reason, both filters will still show.

So far, I have figured out that the dependent filters will work beautifully if you make the controlling filter anything but a field from a content type. I noted that this also applies to taxonomy term reference fields; if they are set as controlling filters, the dependent filters will not be hidden, but you can use Content: Has taxonomy term as a controlling filter instead.

The module is really, really,really handy, but there's something weird going on with the way it interacts with fields... Maybe this module was never meant to work at this granular a level; maybe is this type of behavior by design?