-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
1.1.0 caused ugly looking internal references #1368
Comments
This should fix the issue: #1369 |
Thanks for the fix, @dolfinus! It does seem to fix the bug you noticed. I've put out a bugfix release 1.1.1: https://pypi.org/project/sphinx-rtd-theme/1.1.1/ We can close this issue, but report back if your docs are still looking incorrect with the new release. |
The issue is fixed after upgrading to 1.1.1, thanks! |
Is it okay that 1.1.1 release is not in releases list on Github? |
We don't use releases on GitHub, we only normally tag commits. |
Out of habit, I used GitHub releases for 1.1.0 but I think @agjohnson prefers that we don't.. which is fine, all the info is on PyPi and we have a badge in the README 👍 |
Problem
I have a page with 2 tables - list of classes on the page, and list of methods in each class.
1.0.0 produced tables which looks fine:
But after upgrading to 1.1.0 internal links to classes and methods started to overflow:
This is caused by #1193, after disabling CSS rule
overflow-wrap: anywhere
table appearance is normal again.Same issue is observed in other projects, like PlasmaPy/PlasmaPy#1784. To restore previous behavior, users either lock there version to
<1.1.0
, or uses some hacks like PlasmaPy/PlasmaPy#1785.Reproducible Project
Sorry, my repo is not public.
Documentation is generated using
autosummary
andautoclass
plugins.Generated
href
s and other attributes for<a>
tags are quite long:But
<a>
tag body contains only short class name and method signature, not the full name, so it should not cause overflow.Error Logs/Results
None
Expected Results
Change from #1193 should be applied to only
<a>
tag, but not nested<code>
and<span>
tags.Environment Info
The text was updated successfully, but these errors were encountered: