Use Pick a class to combine authored classes and ancestor context, then confirm the scope before changing shared styles.
Where: Right sidebar → style scope → Pick a class → selector builder.
Key ideas
- Subject classes form a combination: Choose classes on the selected element to build a shared subject such as .card.large. This matches elements with both classes; it is not the descendant selector .card .large.
- Ancestor context narrows the rule: Choose a class from an ancestor to constrain where the subject applies, for example .hero .card.large. The builder presents available authored classes along the ancestor path instead of requiring a manually typed selector.
- Scope is an editing decision: A shared selector can affect several elements. Per-element identity classes are filtered out of this picker so they are not mistaken for useful shared style targets. Check the match count and composed selector before applying changes.
Steps
- Select an element that has authored classes. If none exist, assign a meaningful class first.
- Open Pick a class and select the subject class chips. Add another subject chip only when you want the combined-class condition.
- Choose ancestor context where the rule should apply. The selector preview shows the composed relationship.
- Check the match count and intended scope, then select the composed selector as the style-editing target.
- Change a small visible property and inspect another matching element to confirm the shared scope. Use reset/clear controls on the property if you need to remove that scoped value.
Scope controls beyond the selector builder
The Position row, Layout pads, advanced Typography panel, and composite controls in the floating bar now expose consistent scope/reset affordances. Before changing a value, inspect whether it belongs to the element, class, contextual selector, or a broader page-frame target.
All pages and project modes
All pages targets the page-frame rule even when a page has no user class. New website pages use a flex-column layout default, but that default does not force website stacking onto video compositions or ad variations. Imported website markup is treated as layout-page content on the relevant import surfaces.
Tips
- Use a contextual selector when the same component genuinely needs a local variation.
- Keep combinations small and inspect the preview rather than assuming chip order creates a different relationship.
Troubleshooting
The builder offers no classes.
Assign an authored user class. Internal identity classes are deliberately excluded from this shared-target chooser.
A change affects more elements than expected.
Inspect the composed selector and match count; narrow the ancestor context or return to element scope before continuing.