Vaesper
Vaesper
How would you use this on mobile?
Sure, just figured I should point out that that's also a thing to consider :)
Sounds like you are on the mobile layout (gets triggered if the window width is 968px or smaller). If so, you did not miss a checkbox, it's true that there...
Custom CSS workaround: ``` CSS #sidebar[data-state=hidden] { transform: translate(0,0); -webkit-transform: translate(0,0); } .content[sidebar-state=hidden] #bufferlines, .content[sidebar-state=hidden] .footer { margin-left: 200px; } ```
Actually if the ng-if would be possible, then it might also be useful for #616
No it's still a thing that... https://github.com/glowing-bear/glowing-bear/pull/843 tried to fix it but there was still some unresolved (and hard to reproduce) bug, and iirc @torhve and you ( @lorenzhs )...
Oh and for sake of clarity; the css changes are to "undo" the `vertical-align: top` from the desktop layout. For desktop it's necessary to line up the table cells correctly...
I think that this whitespace should be attributed to the table-cell padding that is not removed when switching to `display: inline` in the mobile layout. I will tinker with this...
@torhve you're either going to love me or hate me for what I've done to mobile layout this time :D
Found some weirdness where the re-ordering of the prefix and timestamp was messed up on some lines on FF mobile. Same bufferline worked fine on FF desktop with the mobile...