Skip to content
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

doc: use same link color in linked code blocks as in regular text links #4068

Closed
wants to merge 1 commit into from
Closed

doc: use same link color in linked code blocks as in regular text links #4068

wants to merge 1 commit into from

Conversation

svenheden
Copy link

Currently there's no way in the docs to visually distinguish a link in a code block from a non-linked code block.

This is how linked code blocks are styled today...

before

...and this is how linked code blocks are styled with this commit applied...

after

@mscdex mscdex added the doc Issues and PRs related to the documentations. label Nov 29, 2015
@silverwind
Copy link
Contributor

I like the change, but wouldn't a a code { color: inherit } suffice?

@svenheden
Copy link
Author

Yeah that would also do it, if one prefers an override rule over the :not() property

@silverwind
Copy link
Contributor

Yeah, I think it's best to avoid :not unless really necessary, makes it easier to read and understand too.

@svenheden
Copy link
Author

Updated and force pushed :)

@silverwind
Copy link
Contributor

Doesn't work here, looks like we need to increase specificity of that style. The options are

a code {
  color: inherit !important;
}
#apicontent a code {
  color: inherit;
}

I think the first option is the way to go in case the container id ever changes, but I'll leave that up to you :)

@silverwind
Copy link
Contributor

Oh wait, it's working correctly. I live edited the wrong stylesheet so my rule came before the p code block which was overriding a code.

LGTM

silverwind pushed a commit that referenced this pull request Nov 30, 2015
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: #4068
Reviewed-By: Roman Reiss <me@silverwind.io>
@silverwind
Copy link
Contributor

Thanks! Landed in f4f1e89.

@silverwind silverwind closed this Nov 30, 2015
@svenheden svenheden deleted the doc/links-in-code-blocks branch November 30, 2015 18:58
MylesBorins pushed a commit that referenced this pull request Dec 1, 2015
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: #4068
Reviewed-By: Roman Reiss <me@silverwind.io>
rvagg pushed a commit that referenced this pull request Dec 4, 2015
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: #4068
Reviewed-By: Roman Reiss <me@silverwind.io>
rvagg pushed a commit that referenced this pull request Dec 5, 2015
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: #4068
Reviewed-By: Roman Reiss <me@silverwind.io>
@jasnell jasnell mentioned this pull request Dec 17, 2015
jasnell pushed a commit that referenced this pull request Dec 17, 2015
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: #4068
Reviewed-By: Roman Reiss <me@silverwind.io>
jasnell pushed a commit that referenced this pull request Dec 23, 2015
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: #4068
Reviewed-By: Roman Reiss <me@silverwind.io>
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
Links nested in backticks were not visually distinguishable before, this
fixes them.

PR-URL: nodejs#4068
Reviewed-By: Roman Reiss <me@silverwind.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants