Club: removing text-decoration-thickness from theme.json #6384
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
3 tasks
…it browsers are not compatible with text-decoration shorthand syntax
matiasbenedetto
force-pushed
the
club/text-decoration-thickness-compat-webkit
branch
from
171cb42 to
39b0708
Compare
…use webkit browsers are not compatible with text-decoration shorthand syntax" This reverts commit 39b0708.
…it browsers are not compatible with text-decoration shorthand syntax
…y to all the link elements in the page. Otherwise the browser defaults to auto
jffng
approved these changes
Aug 12, 2022
matiasbenedetto
deleted the
club/text-decoration-thickness-compat-webkit
branch
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.
Changes proposed in this Pull Request:
Club: removing text-decoration-thickness from theme.json because WebKit browsers are not compatible with text-decoration shorthand syntax
Related issue(s):
Fixes: #6378
Part of: #6243