-
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
py:property's stacking on a single line on larger screen widths. [replicated] #1301
Comments
I have the same issue. As a bonus info I can share that I tried to bisect the problem, by installing older versions of the theme, but as far back as 0.2.0 (which is the oldest I could install) I can replicate the faulty behavior. This suggests to me that the bug is brought on by a change elsewhere, which just now reveals a potential bug in the theme. Environment info:
EDIT: Addition environment information: I should probably also mention, that for my case the pages that showed this behavior were generated by autodoc from docstring written in the Google style and parsed with Napoleon. |
Thanks for replicating it, Is there anyway to avoid this behavior? |
@spidertyler2005 I'm not associated with the project and I'm afraid I don't have the bandwidth to try and fix it, so for me unfortunately I will wait until someone from the project notices this bug. But, you can probably remove the "Needed: replication" label, that might help for visibility. |
This might be the source of the issue: sphinx_rtd_theme/src/sass/_theme_rst.sass Lines 472 to 475 in bc73ad8
I'm seeing the same thing on my doc builds. If you use dev-tools to uncheck (It will be on the parent container |
@spidertyler2005 @KennethNielsen Here's a gist that replicates the issue. When built, the If built with the last line of conf.py uncommented, the display property is overridden by css and they appear as expected. (you'll have to do a Note: |
Unsure why this is necessary. There should never be a case where properties are displayed inline (if attributes and methods aren't) readthedocs/sphinx_rtd_theme#1301
Having the same issue. Is there a proper fix in sight? |
workaround readthedocs/sphinx_rtd_theme#1301 Signed-off-by: Johannes Mueller <[email protected]>
Ran into this today. echoing the previous comment, "Is there a proper fix in sight?" |
@westonplatter @johannes-mueller Can always just use the css override in my last comment. If it's not going to be fixed by the maintainers, monkeyhacking is always a viable solution. (As of this comment, the style for ".property" still has |
:py:`property` blocks get rendered on a single line instead of separate lines Fixes readthedocs#1301
workaround readthedocs/sphinx_rtd_theme#1301 Signed-off-by: Johannes Mueller <[email protected]> Signed-off-by: Benjamin Maier <[email protected]>
For anybody affected arriving here, a mini guide on monkeypatching this until the PR is hopefully merged someday:
|
I'm hitting the same issue with sphinx-rtd-theme 2.0.0. |
…appear on individual line as per readthedocs/sphinx_rtd_theme#1301
…appear on individual line as per readthedocs/sphinx_rtd_theme#1301
Problem
Multiple properties I defined in the docs are all stacking on a single line. I have no idea what could be causing it. Using
|
to force a new line just adds too much space to be reasonable.Before you continue reading, thanks in advance for looking at my issue. Sorry if I just messed up my RST, I am fairly new to writing documentation in sphinx.
Reproducible Project
I think this should be the minimum needed to reproduce it. Just note that it doesn't happen on smaller screen widths.
Error Logs/Results
No errors but here is a picture of what I see.
Expected Results
I expected each entry to be on a separate line regardless of the screen width.
Environment Info
The text was updated successfully, but these errors were encountered: