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: Fix selection of parameter names in HTML theme #21435

Merged
merged 1 commit into from Oct 23, 2021

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Oct 22, 2021

PR Summary

Parameters are written in HTML as (leaving out some internal classes):

<strong>name</strong><span class="classifier"><a><code><span>TypeName</span></code></a></span>

but in rendered form there's a colon between the name and type. This colon is inserted virtually using CSS, but since it doesn't exist, the browser thinks both sides are part of the same word.

Styling the virtual text as inline block makes it be treated as a break, but also makes it apply vertical margins, so we need to set those to zero again.

See also sphinx-doc/sphinx#9763
Fixes #21432.

PR Checklist

  • [n/a] Has pytest style unit tests (and pytest passes).
  • [n/a] Is Flake 8 compliant (run flake8 on changed files to check).
  • [n/a] New features are documented, with examples if plot related.
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • Conforms to Matplotlib style conventions (install flake8-docstrings and run flake8 --docstring-convention=all).
  • [n/a] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • [n/a] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

Parameters are written in HTML as (leaving out some internal classes):
```
<strong>name</strong><span class="classifier"><a><code><span>TypeName</span></code></a></span>
```
but in rendered form there's a colon between the name and type. This
colon is inserted virtually using CSS, but since it doesn't exist, the
browser thinks both sides are part of the same word.

Styling the virtual text as inline block makes it be treated as a break,
but also makes it apply vertical margins, so we need to set those to
zero again.

Fixes matplotlib#21432.
@QuLogic QuLogic added this to the v3.5.0 milestone Oct 22, 2021
@dstansby
Copy link
Member

Thanks for the quick fix!

@dstansby
Copy link
Member

Going to merge with one review as this is essentially vendoring an accepted upstream fix.

@dstansby dstansby merged commit c77233e into matplotlib:main Oct 23, 2021
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Oct 23, 2021
dstansby added a commit that referenced this pull request Oct 23, 2021
…435-on-v3.5.x

Backport PR #21435 on branch v3.5.x (DOC: Fix selection of parameter names in HTML theme)
@QuLogic QuLogic deleted the fix-parameter-breaks branch October 25, 2021 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Doc]: Double clicking parameter name also highlights next item of text
2 participants