@Paul - yes, I had huge problems with styles appearing at odd places. I'd wonder why something wasn't looking the way I expected, would open the .css in a text editor (which is how I'm used to working) and couldn't see anything. Then would find that I'd updated the style at several different times and the *same class* was in more than one place... most of the definitions together (the first pass), then I'd added borders/increased spacing... and that was somewhere else. I found it very confusing. I also didn't like that that editor seemed to put in a lot of (to me) unnecessary stuff. I seemed to get a lot of repetition (border specified all in one, then each border separately...). Maybe it is the way I'm using the editor, but for my own sanity while "tweaking", I prefer the text editor. I *do* use the built in stylesheet editor for the more complex stuff - but almost immediately open the stylesheet, find what I've just added/changed, and put it in the right place.
@Dave - the only issue I've had (and it's workable, but annoying) is that the cascade doesn't work so well in Flare's own editor. The project is linked to the top-level stylesheet, which only contains two (so far) import statements. The styles are "read" but based on the primary target. And the problem isn't the visual appearance (although can be a tad disconcerting at times) but the availability of styles. I have far more in the print-based documentation (stuff like the build in .keepWIthNext, .keepWithPrevious and other related concepts, so I'm keeping my primary target as one of the PDF ones. But I've also got a few in the help.css that aren't in the print-based (so .beforeList, which reduces the padding-bottom of text that introduces a list). Depending on the primary target, it's not that I can't see the _effect_ of the medium-specific classes - it's that they aren't there to select! I can see me having to put all in both, even with blank definitions, so I can apply them.
I'd also like to be able to select more than one class to apply from the editor, but haven't found a way to do that (which means at the moment that my .beforeList also contains the instruction to avoid page break after, whereas for true cascade, I'd just have the spacing difference in that class and apply both it and the keepWithNext class to the same paragraph.
Alison