8000 Sidebar flows out of constrained area · Issue #153 · squidfunk/mkdocs-material · GitHub
[go: up one dir, main page]

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

Sidebar flows out of constrained area #153

Closed
squidfunk opened this issue Feb 13, 2017 · 3 comments · Fixed by #169
Closed

Sidebar flows out of constrained area #153

squidfunk opened this issue Feb 13, 2017 · 3 comments · Fixed by #169
Assignees
Labels
bug Issue reports a bug
Milestone

Comments

@squidfunk
Copy link
Owner

Description

If a table is the last element in the content area, the sidebar exceeds the constrained area

Expected behavior

The sidebar always has the same padding at the top as at the bottom.

bildschirmfoto 2017-02-13 um 15 11 17

Actual behavior

The sidebar exceeds the constrained area.

bildschirmfoto 2017-02-13 um 10 09 12

This is related to the md-typeset__table element. Removing it, corrects the spacing/padding.

Package versions

  • Python: all
  • MkDocs: 0.16.1
  • Material: 1.0.3

System information

  • OS: all
  • Browser: all
@squidfunk squidfunk added the bug Issue reports a bug label Feb 13, 2017
@squidfunk squidfunk added this to the 1.1.0 milestone Feb 13, 2017
@squidfunk squidfunk self-assigned this Feb 13, 2017
@squidfunk
Copy link
Owner Author

Okay, now this is a very, very strange bug in Chrome. It doesn't happen in Firefox or Safari. The vertical (top and bottom) margin for the table are given in em units, while the horizontal margin is given in rem units. When I change em to rem, everything behaves as expected.

It doesn't matter whether the table is at the end. When there is at least one table in the document, it breaks. What the...

@facelessuser
Copy link
Contributor

What the...

That is my constant response as a non-web programmer navigating the differences of different browser quirks :).

@squidfunk
Copy link
Owner Author

This is indeed a bug in Chrome 56. Tested it on Windows and OSX with 55 through Saucelabs - everything works fine. F**k.

bildschirmfoto 2017-02-14 um 12 47 33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue reports a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0