fix: unify noToc/noTOC config to canonical noTOC - #5394
Draft
marcoscaceres wants to merge 1 commit into
Draft
Conversation
marcoscaceres
force-pushed
the
fix/5258-notoc-consistency
branch
from
August 17, 2026 03:17
fe735fb to
c884195
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #5258
The config property was split: style movers used
noToc(lowercase c) whilestructure.jsusednoTOC, so a spec author setting one spelling did not affect the other. This unifies the w3c, aom, dini and geonovum profiles on the canonicalnoTOCand normalizes the legacynoTocin each profile's defaults for backwards compatibility, and CI now builds all four profiles so the aom and dini changes are actually exercised.Written with AI: this change was generated by Claude. Per AI_POLICY.md.