-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Landing page: Headings now have dark thick underlines #98
Comments
This may be due to CSS specificity changes in Gutenberg 18.5 and soon to be in WordPress 6.6. We can into similar link-related issues here. |
These have always had underlines (see the screenshots on #71), but you're right that the underline changed. It does seem related to the GB update. |
ryelle
added a commit
to WordPress/wporg-parent-2021
that referenced
this issue
Jun 18, 2024
This fixes the interaction of link styles applied by other elements in theme.json, by ensuring the base styles are set in the same way. Additionally, this increases the specificity of the text-decoration longhand properties, so that they apply after the shorthand `text-decoration` from theme.json. Fixes #143, WordPress/wporg-documentation-2022#98
Thanks for fixing the regression! |
DanyloKubyshkin
added a commit
to DanyloKubyshkin/wordpress-org
that referenced
this issue
Jul 12, 2024
This fixes the interaction of link styles applied by other elements in theme.json, by ensuring the base styles are set in the same way. Additionally, this increases the specificity of the text-decoration longhand properties, so that they apply after the shorthand `text-decoration` from theme.json. Fixes #143, WordPress/wporg-documentation-2022#98
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At launch, the Documentation section had dark headings with no underlines. Some time recently, rather thick dark underlines were added:
Is this an unintentional regression?
If it's because the links must be underlined, we should unlink the headings and instead add a separate "See all" hyperlink.
The text was updated successfully, but these errors were encountered: