From f788035a58f87168ad5301aae3d24ef1ec153291 Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Tue, 12 Apr 2022 13:30:37 +0200 Subject: [PATCH] Remove unnecessary `min-width` CSS rules - For the findbar/secondaryToolbar case, the `min-width` rule doesn't really make sense since it's way too small to be useful. Furthermore, the findbar is already specifying its own `min-width` and the secondaryToolbar will (thanks to its buttons) receive a correct/useful width. - The pageNumber-input already has an *explicit* `width` set, hence setting the `min-width` rule as well is completely unnecessary. - The treeItem-links are supposed to *compute* their `min-width`, and the static value was only added as a fallback for older browsers without `calc()` support. --- web/viewer.css | 3 --- 1 file changed, 3 deletions(-) diff --git a/web/viewer.css b/web/viewer.css index 97d81cf3d..409981841 100644 --- a/web/viewer.css +++ b/web/viewer.css @@ -429,7 +429,6 @@ select { position: absolute; z-index: 10000; height: auto; - min-width: 16px; padding: 0 4px; margin: 4px 2px; color: rgba(217, 217, 217, 1); @@ -1066,7 +1065,6 @@ select { .toolbarField.pageNumber { -moz-appearance: textfield; /* hides the spinner in moz */ - min-width: 16px; text-align: right; width: 40px; } @@ -1189,7 +1187,6 @@ a:focus > .thumbnail > .thumbnailSelectionRing, .treeItem > a { text-decoration: none; display: inline-block; - min-width: 95%; /* Subtract the right padding (left, in RTL mode) of the container: */ min-width: calc(100% - 4px); height: auto;