Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qz12A-00Cm2d-GR for pgsql-www@arkaria.postgresql.org; Fri, 03 Nov 2023 20:44:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qz128-003J9v-O6 for pgsql-www@arkaria.postgresql.org; Fri, 03 Nov 2023 20:44:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qz127-003J9n-0M for pgsql-www@lists.postgresql.org; Fri, 03 Nov 2023 20:44:48 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qz11z-003oqi-Is for pgsql-www@postgresql.org; Fri, 03 Nov 2023 20:44:45 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 3BC1F5C00ED; Fri, 3 Nov 2023 16:44:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 03 Nov 2023 16:44:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm3; t=1699044278; x=1699130678; bh=LtB0fMN4zf3pnZ4EfvPoOIVgS d95hoIB3tuC3+AVvRY=; b=Mn28k9Z6Kt3RF9GOHls7+/0T8KjTFcq+BzqMgpFvJ Euccr+3nBn84sNb4o1Xg1LCaXwUXMdHN7MFr0kxXkN90os0Ri1TjW1MeUou+KQR4 eORHeh4gheqIZqi7YU0HS2/By1MlM965R8jeEts412b3Rcjk2R0KYIXc0i3TdZez TZFyZjTo7fEXvnL1DjjEUVhgcaYhg70YVU5xyXzKZSC7fRjuhxIHjzBkBnEPsnjH 43xLYXCMq9SzxKnZJn/OWGjTesbagPKtK4BFVUnMpb7RmNNRDN23Ormzbc4AbG61 Eg3RTu/lsybBZ6LHffmAq6jzD1eolcObeDKV4RwmmS52w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1699044278; x=1699130678; bh=LtB0fMN4zf3pnZ4EfvPoOIVgSd95hoIB3tu C3+AVvRY=; b=HSqSQzdR/cgOQFf3iB3nwa4mAiqsKgp7d+lAkBB1xcwkHZfLC5p I48U0TekIS7jkuNyzGYBXS7PZMlwni8F78PQ4JIXFHMomXy6ukYVloIibcHAI/O9 iVigYfmyUISUqw0ebMEREdTLdRnR70gV+Tv4j+3Irpp9UhRryH2JCwGYKz0tuvds bkx7SZQfMwCyY/dTVUZZkTCg7Ou3i+2qjk/gGqFToIwqwdIyeXOc/gUIPhm0h/Ud luHnMgJj6SgaLKWR4TWsB1mvqXqRS4Htqv/KejRCVYcTgGoP4TsNqPWILIw8+zyQ HmpzDQTacMuIsRoS09VuVRJprDHGHiSL5CA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedruddtkedgudefkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtugesthdtredttddtvdenucfhrhhomheptehnughrvghs ucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrfgrth htvghrnheptefhleelteeghfehledugfevjeekvdevieeffeehffdtteekteffveeiteeu feetnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgii vghlrdguvg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 Nov 2023 16:44:37 -0400 (EDT) Date: Fri, 3 Nov 2023 13:44:35 -0700 From: Andres Freund To: pgsql-www@postgresql.org, "Jonathan S. Katz" Subject: docs: variablelist rendering Message-ID: <20231103204435.tz6qgxbht3n62hi5@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, The styles used to render variablelist on pages like https://www.postgresql.org/docs/devel/install-meson.html#MESON-OPTIONS imo make it hard to visually attribute the description of an option to the option, as the vertical space between the description and the variable is about the same as the to the next option. This seems to be from https://git.postgresql.org/gitweb/?p=pgweb.git;a=blob;f=media/css/main.css;h=80afc3d113cd1992b890ff2b90c04b991290b1b2;hb=HEAD#l1345 and a few related rules. I'm not sure this was intended, it looks like there are a few rules interacting with each other, some from bootstrap. First dd has a top margin of 1 from #docContent .variablelist dd { margin-top: 1rem; } and a bottom margin of 0.5rem from bootstrap (except for other margins it'd be close to the next dt). Then p has a 1rem distance from both bottom and top: #docContent .VARIABLELIST p, #docContent .variablelist p, #docContent .VARIABLELIST pre, #docContent .variablelist pre { margin: 1rem 0 1rem 2rem !important;; } making the distance from both the same. The indentation of items is also very deep - is that intended? Kinda looks like it accidentally might have gotten doubled. There's 2rem from #docContent .VARIABLELIST dd, #docContent .variablelist dd { margin-inline-start: 2rem; } *and* 2 rem from #docContent .VARIABLELIST p, #docContent .variablelist p, #docContent .VARIABLELIST pre, #docContent .variablelist pre { margin: 1rem 0 1rem 2rem !important;; } which are not collapsed (I think that just happens vertically). So it's 4 rem deep... After adjusting this in the browser, I noticed that the itemized lists inside https://www.postgresql.org/docs/devel/install-meson.html#CONFIGURE-WITH-UUID-MESON ended up very deeply indented. But that actually something happening outside of this context / without changing anything else. Check e.g.: https://www.postgresql.org/docs/devel/btree-behavior.html There's a 2.5rem left margin from: #docContent ul.itemizedlist { margin-left: 2.5rem; } *and* padding - I think from the desktop browser defaults (both in firefox and chrome on linux). I doubt that was intended? Greetings, Andres Freund