From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <s.sterz@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 1262B94A19 for <pmg-devel@lists.proxmox.com>; Thu, 22 Feb 2024 17:37:17 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E7F92CC47 for <pmg-devel@lists.proxmox.com>; Thu, 22 Feb 2024 17:36:46 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pmg-devel@lists.proxmox.com>; Thu, 22 Feb 2024 17:36:45 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 408CB44ACE for <pmg-devel@lists.proxmox.com>; Thu, 22 Feb 2024 17:36:45 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 22 Feb 2024 17:36:44 +0100 Message-Id: <CZBR661VN8YF.2RDHQU7HYMZEV@proxmox.com> From: "Stefan Sterz" <s.sterz@proxmox.com> To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>, "Dominik Csapak" <d.csapak@proxmox.com>, <pmg-devel@lists.proxmox.com> X-Mailer: aerc 0.17.0-57-g782a17dfb056 References: <20240222142941.2912401-1-d.csapak@proxmox.com> <6a51ea2a-67f7-4fbc-a602-b0aae27c37c5@proxmox.com> In-Reply-To: <6a51ea2a-67f7-4fbc-a602-b0aae27c37c5@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.080 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pmg-devel] applied: [PATCH pmg-gui] objects: use font-weight for bold text X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion <pmg-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pmg-devel>, <mailto:pmg-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pmg-devel/> List-Post: <mailto:pmg-devel@lists.proxmox.com> List-Help: <mailto:pmg-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel>, <mailto:pmg-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Thu, 22 Feb 2024 16:37:17 -0000 On Thu Feb 22, 2024 at 3:51 PM CET, Thomas Lamprecht wrote: > Am 22/02/2024 um 15:29 schrieb Dominik Csapak: > > mdn[0] recommends using `font-weight: bold;` for making the text actual= ly bold > > While it has the same effect often, it depends on the font and browser > > if the font is rendered bold in a <b> tag. > > > > 0: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/b > > > > Signed-off-by: Dominik Csapak <d.csapak@proxmox.com> > > --- > > js/ObjectGroup.js | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > > > applied, thanks! > > FWIW, one general option might also be to add CSS setting the font-weight= to > the <b> tag in general, but not sure what would break with that.. > just to add my two cents to this: generally it would be nice to avoid inline css imo. maybe we could also add a css class to the element that has some semantic meaning and use that to style the element. as is recommendet by mdn: > It is a good practice to use the class attribute on the <b> element in > order to convey additional semantic information as needed (for example > <b class=3D"lead"> for the first sentence in a paragraph). > > - [0] alternatively, we could use the more semanticaly meaninful `<strong>`[1] element and define that as bold (which is the default, but the recommendation is to make that explicit there too). this would imply a "strong importance". [1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/strong > > _______________________________________________ > pmg-devel mailing list > pmg-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel