Prevent the [[CSSOM-VIEW]] reference from pulling its internal references #313
Conversation
This file contains 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
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.
ok. This is a slight change since the note will directly link to CSSOM View spec instead of linking to the informative references section, but it does make respec stop loading the "cssom-view" internal references within the section, thus preventing the ambiguity of ui-events/MouseEventInit
Fyi for @marcoscaceres , we have a div.note that cites "[[CSSOM-VIEW]]", thus triggering the load of all internal references for cssom-view within the section. Any attempts to disambiguate using data-cite="ui-events" (for pre.idl or for {{MouseEventInit}}) within that section fails.
Fix #311
Preview | Diff