It seems the mc:conditions configured in my stylesheet are being beaten by inline conditions!?
The whole story is below, but after not getting the conditional output expected in our targets, I did some digging, and found a note tucked on the bottom of this page in the MadCap help, http://help.madcapsoftware.com/flare201 ... Styles.htm, which states:
So, if I’m reading this right, using stylesheet conditions will not work if we also apply conditions to those same elements inline.Conditions that are set locally (i.e., directly on content) will override conditions set on a style. Even if the local condition is empty, it still overrides the conditions set from stylesheet.
Is this the case? Anyone else run into this? If so, what was your workaround?
We are trying to avoid having to explicitly set another condition on every element that we may want to conditionalize in secondary way.
Background…
- Our project is conditionalized for two differently-branded product names (Product A and Product B), and has two targets, PDF and HTML5.
- Each product has its own images/branding, each of which is appropriately conditionalized to Product A or B in our project.
- We only want images to appear in PDF output, not in HTML5 output. This is true for both Product A & B.
Unfortunately, in this multi-product project, the css mc:conditions setting seems to be trumped by the inline condition, resulting in a correctly branded HTML5 build, but including the undesired images.