Make arithmetic operator formatting consistent in CSS docs#44335
Open
VladNegara wants to merge 2 commits into
Open
Make arithmetic operator formatting consistent in CSS docs#44335VladNegara wants to merge 2 commits into
VladNegara wants to merge 2 commits into
Conversation
github-actions
Bot
added
Content:CSS
Contributor
|
Preview URLs (2 pages) |
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
2 participants
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.
Description
I added backticks around the
+,-,*,/operators in the docs of themin()andmax()CSS functions to have them rendered in code font.Motivation
I am proposing these changes for consistency with the docs for the
clamp()function. The docs forcalc()andcalc-size()also use code font.Additional details
I personally think spacing out the parentheses from the symbols looks unprofessional. This is how it is currently written in the docs:
If the operators are typeset in code font, I believe this sets them apart enough from the surrounding parentheses to justify removing the spaces altogether, like this:
This change is not included in this PR.