jth at mikrobitti.fi
Mon Dec 8 07:55:39 UTC 2003
At 16:31 7.12.2003 -0600, you wrote:
>On Dec 7, 2003, at 2:59 PM, Jouni Heikniemi wrote:
>>Mm, yeah, I didn't mean a blind replace of "subsubheading" with
>>"bugsummary". But when the content of subsubheading is a bug summary, the
>>class name could reflect it. When it's something else, let's reflect that
>>then. We are not supposed to assume that all subsubheadings are created
>>equal (on style level), right?
>I was under the impressions that being that generic was precisely the
>goal. If you call it 'bugsummary', you've pretty much made it impossible
>to use anywhere else.
That depends heavily on what the surroundings are. If you have, say,
<h2>Bug 2314 - <span class="bugsummary">Foobar</span></h2>
you can refer to that bugsummary as "h2 bugsummary", and still refer to
other bug summaries elsewhere with only "bugsummary". Being generic and
specific are not mutually exclusive if you use multiclassing; markup like
|<span class="bugsummary subsubheading">blah</span>| could combine best of
>Absolutely. I was referring back to a few of Christian's suggestions for
>using <div's> for elements of the heading, which need to be inline to stay
Or be absolutely positioned. This is a reasonable alternative, too.
>I voiced this mainly because I've not looked into what crazy CSS will be
>required for other pages. I spend my of my patch time on the bug info
>page. I'm not qualified to devise a set of classes and such that Just
Nobody else will either. I believe we'll soon be able to crank out a set of
rules that will act as a good basis for doing the CSS work. Let's just be
flexible and ready to change them when we realize we've made mistakes. But
as Kiko said, our content is fairly simple for the most part.
More information about the developers