Hmmm, OK Cindy, i think you've missed the fact that "gpii.primarySchema.magnifierEnabled" is a preference already existing in the schema. There is an adjuster for it and all, so using that does not "pollute" the schema with extra preferences that would need filtering before sending to the preferences server. I agree though that using the conditional panels technique looks more elegant and is something that we know it's working correctly (backed up by unit tests etc.), while my extra "expandingAdjusters" grade looks more like an ad-hoc solution for the particular problem (which is reusable though). On the other hand, if we go with Alex's approach, we seem to override the semantics of a "preference" inside a "model/schema", having to mark some preferences as "special type"-"do not send over when saving". Perhaps @yzen or @jobara can have a thought on that?