Sidebar flows out of constrained area #153

Closed
squidfunk opened this Issue Feb 13, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@squidfunk
Owner

squidfunk commented Feb 13, 2017

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

This comment has been minimized.

Show comment
Hide comment
@squidfunk

squidfunk Feb 13, 2017

Owner

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...

Owner

squidfunk commented Feb 13, 2017

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

This comment has been minimized.

Show comment
Hide comment
@facelessuser

facelessuser Feb 13, 2017

Contributor

What the...

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

Contributor

facelessuser commented Feb 13, 2017

What the...

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

@squidfunk

This comment has been minimized.

Show comment
Hide comment
@squidfunk

squidfunk Feb 14, 2017

Owner

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

Owner

squidfunk commented Feb 14, 2017

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