Christian Robottom Reis
kiko at async.com.br
Mon Dec 8 15:01:01 UTC 2003
On Sun, Dec 07, 2003 at 11:20:45PM +0000, Gervase Markham wrote:
> Jouni Heikniemi wrote:
> >On Sun, 7 Dec 2003, Gervase Markham wrote:
> >>Imagine a screen reader. "What's this page about?", asks the blind user.
> >>"This is Bugzilla", replies the reader, when it should really be
> >>replying "Bug 12345" or "Search for bugs".
> >Actually, while what you say is true, I disagree. If you click a link on
> >some page and end up on something called "Bug 34567", you're pretty much
> Well, presumably you wouldn't be baffled if the preceding page had
> explained what was going on, and why it had that particular link as part
> of it :-)
Yes, but what if you're coming in from another site? You just can't
guarantee that a Web user went through the expected steps here. I
strongly agree with Jouni and Cory that <h1> should be the general site
> >While it's true that when navigating inside Bugzilla the first
> >really interesting heading is the page title, I still don't think we can
> >skip the heading describing the particular installation.
> You mean "This is Bugzilla"? As I said, that's not guaranteed to be
> there - it could be an image. In fact, it was an image in the default
> install up until a year or so ago. As it happens, I don't like what
> we've replaced it with, and when we get a logo sorted out, I'd be up for
> returning to an image. But the point is, it's transient - so not a good
> choice for our H1.
Err, what's wrong with <h1> holding an image?
I have yet to run into a Bugzilla installation that didn't have a header
describing what the site was, so I don't think it's transient -- more to
the point, I do think that most sites will customize the bugzilla header
to contain something organization-specific -- it's just more logical to
emphasize that this is a bug tracking system for project/company X than
to emphasize that this is Bugzilla the world-class bug-tracking system
and that it happens to be used in this particular instance for puny
company X which isn't entitled to its own header in its <h1> area :-)
This doesn't mean I'm not for a Bugzilla logo -- of course Bugzilla
needs its own identity, which should go with its default install. But
sites running PHP4 or Apache don't have that in their <h1>s, and I don't
think most Bugzilla sites will either.
> >The problem here is that it's potentially hard for the wrapper pages to
> >know all required css file references. It takes quite a bit of work to
> >figure out which style sheets could be necessary in all possible parameter
> >combinations. For example, if some new popup-based UI feature gets checked
> >in and used in several pages (like our current user selector), it can be
> >potentially hard for all pages to include exactly the proper combination
> >of css files.
> I don't see this as being an issue in practice, to be honest.
I agree, and I think that having separate files is a good thing.
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
More information about the developers