right, Klaus, specificity resolves conflicts. which could be an issue, if your main site css uses !important on any element which conflicts with your candy css.
fortunately, !important seems to be used rarely, so that's probably not going to be an issue. if, by rare chance, your site's css has a conflicting !important, then you might be able to override it with some javascript or runtimeStyle. but, if your candy's css has conflicting declarations WITHIN ITSELF, then, unless it's a bug in the candy, it's a conflict intended to be resolved by specificity-- and applying !important to all elements within the candy will have no effect on the intended behavior of the candy.