-
-
Notifications
You must be signed in to change notification settings - Fork 908
[BUG] <a> links and <u> underlined texts do not set the correct colors when nested #1414
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
Comments
to solve the problem for your example: |
This does not solve the problem, it is a workaround that does not fix the bug and does not fit most usecases : having an underline color that's different for standard texts and links. Take web for example : 99% of websites use a black/dark grey color for texts (even when underlined) whereas links are usually blue... |
We need to explicitly set the underline color to the same blue as we set the text. fixes: Sub6Resources#1414 We need to explicitly set the text decoration color.
We need to explicitly set the underline color to the same blue as we set the text. fixes: Sub6Resources#1414 We need to explicitly set the text decoration color.
Fixed in 21b6987 |
We need to explicitly set the underline color to the same blue as we set the text. fixes: Sub6Resources#1414 We need to explicitly set the text decoration color.
There are actually two problems :
1. Short links: Link color is missing
When having short
<a>
links nested in<u>
underlined text, the underlining color for the link is the color of the<u>
underlining element, where it is expected to be the color of the<a>
, as it is the inner child.E.g.:
Renders as follows:
2. Long links: Link color is used for text after the text
When having
<a>
links that span multiple lines nested in<u>
underlined text, the link is now actually using its defined color as expected, but this time the underlining color for the text after the link is the color of the link rather than the<u>
underlining color. E.g.:Renders as follows:
The text was updated successfully, but these errors were encountered: