From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: bugfix: list regression
Date: Tue, 22 Aug 2006 11:30:08 +0200 [thread overview]
Message-ID: <eceir6$rv2$1@sea.gmane.org> (raw)
In-Reply-To: 20060822085540.1104.qmail@web31812.mail.mud.yahoo.com
Luben Tuikov wrote:
> Fix regression introduced by
> commit 17d07443188909ef5f8b8c24043cb6d9fef51bca.
>
> 1. Commit 17d07443188909ef5f8b8c24043cb6d9fef51bca defines
> "a.list" twice in gitweb.css, once with bold and once with
> normal font-weight.
>
> 2. "a.list" being "bold", makes a myriad of things shown by
> gitweb in bold font-weight, which is a regression from
> pre-17d07443188909ef5f8b8c24043cb6d9fef51bca behavior.
>
> The fix is to define separately "a.list_bold" and use
> that style in format_subject_html().
This fix is counter to what I wanted to do. I thought that
"list" class is used only in "subject" links, so I defaulted
it to bold (all such elements except one were inside <b>...</b>),
and encoded exceptions; notice
+table.tags a.list {
+ font-weight: normal;
+}
+
We could as well define "bold" class for "a", i.e.
+a.bold {
+ font-weight: bold;
+}
but this is presentational CSS, no better than <b>...</b> element.
The correct solution would be to add "subject" class perhaps,
and do exceptions for it.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-22 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 8:55 [PATCH] gitweb: bugfix: list regression Luben Tuikov
2006-08-22 9:19 ` Junio C Hamano
2006-08-22 9:30 ` Jakub Narebski [this message]
2006-08-22 10:02 ` [PATCH] gitweb: bugfix: a.list formatting regression Jakub Narebski
2006-08-22 22:34 ` Junio C Hamano
2006-08-22 22:46 ` Jakub Narebski
2006-08-22 23:14 ` Junio C Hamano
2006-08-23 4:43 ` Luben Tuikov
2006-08-23 4:45 ` Luben Tuikov
2006-08-23 5:23 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='eceir6$rv2$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).