CKTIS / CSS
trigger-scope — trigger-name scope
trigger-scope restricts trigger-name visibility to a subtree, helping isolate independent components.
Version: CSS modules; structured CSSWG indexes reconciled with pinned MDN BCD; Chromium 152 scope gate, per-example verification still required
Syntax
trigger-scope: none | all | <dashed-ident>#;trigger-scope controls trigger-name scope; it does not create a trigger. Names are global by default within their tree scope, subject to Shadow DOM boundaries.
none leaves scope unchanged. all restricts all relevant names; a comma-separated list such as --reveal, --hide restricts selected names. Descendants resolve them only inside the subtree; outside elements cannot see them. Nested scopes take precedence. Matching uses the flattened tree and respects Shadow DOM tree scope.
The initial value is none; the property applies to all elements and is neither inherited nor animatable. Despite non-inheritance, its restrictions affect descendants. This is a draft specification: verify behavior in your target browser before deployment.
Examples
<!doctype html>
<meta charset="utf-8">
<title>trigger-scope</title>
<style>
#component { trigger-scope: --reveal; }
</style>
<section id="component">
<div id="child">Component content</div>
</section>
<pre id="result"></pre>
<script>
const supported = CSS.supports('trigger-scope', '--reveal');
const scope = id => getComputedStyle(document.getElementById(id))
.getPropertyValue('trigger-scope').trim();
document.getElementById('result').textContent = supported
? `component: ${scope('component')}\nchild: ${scope('child')}`
: 'Unsupported: trigger-scope';
</script>Result
component: --reveal child: none
The displayed code and declared result were verified in an isolated environment using the method recorded in the verification evidence for this exact version.