Christian Robottom Reis
kiko at async.com.br
Sun Dec 7 22:47:50 UTC 2003
On Sun, Dec 07, 2003 at 04:31:10PM -0600, Cory 'G' Watson 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,
> >class name could reflect it. When it's something else, let's reflect
> >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.
Just to clarify, in that specific case, the *only* thing we can infer
for the subheading and subsubheading is the fact that they are level-2
and level-3 headings -- the template doesn't tell
global/header.html.tmpl anything beyond `hx = "foo foo foo"'. So I do
think that subheading and subsubheading apply here.
Nothing prevents, however, the template itself in adding an element that
allows us to distinguish what it is (<div id="bugform"> or whatever).
> 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 horizontal.
In hindsight, it was probably a silly suggestion, but I actually meant
<td><div class="subheading"></div></td>. I know <wink>.
> 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 Work everywhere.
You'll probably be surprised; our content is quite uniformy "plain". The
more complicated pages are search and show_bug. Once we've got header
and footer sorted out, we can tackle the individual pages as we go
(buglist is probably a good candidate for cleanups!)
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
More information about the developers