CKTIS / CSS
CSS specification architecture and feature auditing
CSS evolves as a set of modules rather than one specification with a shared version number. An audit connects the definition index, defining module, pinned compatibility data, and a concrete example test without equating specification inclusion with browser support.
Version: CSS modules; CSSWG indexes identify definitions, pinned compatibility data records implementation support, and the included cascade-layer example passed in isolated Chromium 157.0.8103.51.
Syntax
architecture and audit: feature → CSSWG index → defining module → pinned compatibility record → local example verificationHere, architecture and audit means the organization of CSS specifications and the tracing of evidence about features. Beyond CSS Level 2, the language develops modularly: individual modules have independent levels and maturity. A module’s level is not a version number for CSS as a whole. A snapshot organizes specifications by stability, not browser availability.
Start with the CSSWG directory and CSS Indexes. The index groups properties, at-rules, functions, selectors, and other constructs and links to their definitions. It is non-normative and can contain omissions or mistakes; check syntax, meaning, and restrictions in the defining module. An Editor’s Draft is a working document that can change.
A proposed audit record should separate definition from implementation: feature name, module and revision, exact MDN Browser Compatibility Data (BCD) version or commit, compatibility record path, and local test result. Reconcile index entries with BCD by meaning, not merely by name. No pinned BCD dataset was supplied, so this entry does not claim completed reconciliation.
The example checks one cascade rule: for normal author declarations, the later components layer takes precedence over base before selector specificity is compared. Consequently, .sample wins over #sample. Do not generalize this ordering to !important, which reverses layer priority; normal unlayered declarations take precedence over normal layered declarations. This exact example produced the expected result in isolated Chromium 157.0.8103.51 with external requests blocked.
Examples
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>CSS architecture audit</title>
<style>
@layer base, components;
@layer base {
#sample { color: rgb(255, 0, 0); }
}
@layer components {
.sample { color: rgb(0, 128, 0); }
}
</style>
<p id="sample" class="sample">Layer audit</p>
<pre id="result"></pre>
<script>
const actual = getComputedStyle(document.getElementById('sample')).color;
document.getElementById('result').textContent = actual;
</script>
</html>Result
rgb(0, 128, 0)
The displayed code and declared result were verified in an isolated environment using the method recorded in the verification evidence for this exact version.