schema-apps: fix CSS unicode escapes in content properties#325
Merged
Conversation
The .cc-qual-list li::before checkmark used \u2713 (JS form) which is invalid in CSS and rendered as literal 'u2713'. Converted to \2713 with trailing space (correct CSS escape form). grep confirms no \u escapes remain in any content: property. Gate passes (325 apps).
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.
By Charlie 🤖. POLISH step — CSS bug fix in
app.cssonly.The
.cc-qual-list li::beforecheckmark usedcontent: "\u2713"(JS-style escape) which is invalid in CSS — renders as literal textu2713. Converted tocontent: "\2713 "(correct CSS form: backslash + hex code + trailing space). Verified no\uescapes remain in anycontent:property.Gate passes locally (325 apps).