Build your personal knowledge base with Trilium Notes
TypeScript electronelectron-appknowledge-baseknowledge-graphknowledge-managementknowledge-management-graphlocal-firstnote-managmentnote-takernote-takingnotebooknotesnotes-apppersonal-knowledge-basepersonal-wikiscriptableself-hostedself-hostingwiki
fix(sidebar): open a section beside another one in Safari
Elian Doran0ab7ba525db4
diff --git a/apps/client/src/widgets/sidebar/RightPanelContainer.css b/apps/client/src/widgets/sidebar/RightPanelContainer.cssindex 4934192ac7..b8a0cec54f 100644--- a/apps/client/src/widgets/sidebar/RightPanelContainer.css+++ b/apps/client/src/widgets/sidebar/RightPanelContainer.css@@ -219,9 +219,8 @@ body.desktop.background-effects.last-split-bgfx #center-pane ~ .right-pane-peek-/* Several cards open at once share the pane between them instead of being laid out one under thenext, where the one section a note has dozens of rows in (a template's definitions, say) islaid out in full and pushes everything after it off the pane. Each card gives up room and- scrolls within itself instead — as little as it can, which is the rule below; this much is- what every engine can be counted on for, and it crops each card a little rather than any one- of them badly.+ scrolls within itself instead, which crops each card a little rather than any one of them+ badly.Every card but the growing one, which keeps both its claim on the room the others leave overand the floor it stops at (see `.card.grow` above). Company is no reason to take that away: a@@ -255,25 +254,6 @@ body.desktop.background-effects.last-split-bgfx #center-pane ~ .right-pane-peek-}}- /* Where a card can be capped at its own content, the room is shared by need rather than in- equal parts: every card is offered the same share of the pane, hands back whatever it has- nothing to put there (`max-content`), and what is handed back is offered again to the cards- still short. So the sections with a row or two in them are shown whole and the long one takes- everything left over — instead of each section being cropped a little for the sake of a- section that had room to spare.-- Firefox parses `max-height: max-content` but does not cap a box's height with it, which would- leave every card at an equal share. `-moz-orient` is a Firefox-only property, so Firefox takes- the content-height fallback above instead. */- @supports (max-height: max-content) and (not (-moz-orient: inline)) {- .right-pane-tab-body:has(> .card:not(.collapsed) ~ .card:not(.collapsed)) > .card:not(.collapsed):not(.grow) {- /* Offered from nothing rather than from its content: a card asking for its content up- front leaves the pane over-subscribed, and nothing to hand back out. */- flex: 1 1 0;- max-height: max-content;- }- }-.gutter-vertical + .card .card-header {padding-top: 0;}