-
Notifications
You must be signed in to change notification settings - Fork 317
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
Fix styling of the tables #16
Comments
So the normal tables are fine (and now look good as bootstrap tables after #21), but the autosummary generated tables have some problems: (https://dev.pandas.io/docs/reference/frame.html) The problem is in autosummary defining a colgroup in the generated html:
and for some reason all existing sphinx themes I looked at handle this fine (basically ignore it?), but bootstrap wants to follow it (although it also expands somewhat when needed, because sometimes it is more than 10%, see picture above). |
random issue here: https://dev.pandas.io/docs/user_guide/reshaping.html pivoting with single aggregations (table not rendering in the note) |
@jreback that's broken in the old docs as well (https://pandas.pydata.org/pandas-docs/stable/user_guide/reshaping.html#pivoting-with-single-aggregations), so probably rather an issue with the rst formatting. Will open an issue on the pandas side. |
From #27: we might want to have "striped" tables as a default. Either we add some css to apply that to all tables, or we can ensure in the rst to add the |
This is an old issue, the current table display looks like this: Do you still think that having them striped is necessary? |
In my opinion, we can close this one and re-open a new one if somebody else reports a problem, since the style has changed a decent amount |
See eg https://dev.pandas.io/pandas-sphinx-theme/reference/io.html
We might need to remove some old custom styling (from nature), and ensure that bootstrap's tables are used. But those might again require some styling to fit for autosummary tables etc
The text was updated successfully, but these errors were encountered: