Trying to fix "Formal Syntax" showing an error #24887
Closed
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
Shows: `Error: could not find syntax for this item` I guess this is not a letter case issue (just shooting in the dark here), but if this can/should be fixed in the spec perhaps I could get some info here on how to take this with the CSSWG so that we can file the issue there properly.
|
Preview URLs |
Josh-Cena
reviewed
Feb 26, 2023
There was a problem hiding this comment.
Please see https://github.com/orgs/mdn/discussions/247. This is definitely more involved than changing cases—our macros always work with all-lowercase :)
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.
Shows:
Error: could not find syntax for this itemI guess this is not a letter case issue (just shooting in the dark here), but if this can/should be fixed in the spec perhaps I could get some info here on how to take this with the CSSWG so that we can file the issue there properly.Description
Motivation
Additional details
Related issues and pull requests