312030 - When classifications are enabled, the bug ID is badly aligned when viewing a bug report

Status: RESOLVED FIXED

(Bugzilla :: User Interface, defect)

Description

[Bernhard Merkle]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Hi there,

when you activate the categories option, which is new in version 2.20
I get a layout problem in the show_bug.cgi. The problem is, that the 
bug number is displayed as superscripted (compared to the label Bug#:)

please see attached screenshot for details.


Reproducible: Always

Comment 1

[Bernhard Merkle]

Attachment: wrong layout when categories are activated

Comment 2

[Frédéric Buclin]

This bad UI has already been discussed in bug 156670 comment 11. myk and myself
couldn't find an agreement.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

Attachment: patch v1: one-liner that fixes problem

Comment 4

[Dave Miller [:justdave]]

Comment on attachment 202754 [details] [diff] [review]
patch v1: one-liner that fixes problem

Hmm, a long category name would cause that to get indented quite a ways...  there a reason this isn't just on a row by itself?

How about doing a vertical-align: bottom on the bug number?

Comment 5

[Myk Melez [:myk] [@mykmelez]]

Long classification names will cause indentation problems whether or not we let the header get break, since they're what's causing the indentation ("Bug#" itself is fairly narrow).  vertical-align: bottom would line the bug number up, but it won't fix the ugliness factor of a multi-line header.  Perhaps making classification its own field is the best option, although presumably whoever implemented classifications did it this way for a reason.

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Ping?

Comment 7

[Frédéric Buclin]

(In reply to comment #5)
> but it won't fix the ugliness factor of a multi-line header.  Perhaps making
> classification its own field is the best option, although presumably whoever
> implemented classifications did it this way for a reason.
> 

Having a separate field for the classification is my preferred solution, as already said in bug 156670. ;)

Comment 8

[Myk Melez [:myk] [@mykmelez]]

Comment on attachment 202754 [details] [diff] [review]
patch v1: one-liner that fixes problem

No sense leaving these things around forever.

Comment 9

[Frédéric Buclin]

We no longer display the classification in the bug report since Bugzilla 3.2, and so this is no longer a problem.