bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

Optimize the right column for fluid page widths/wider windows




User Interface
10 years ago
4 years ago


(Reporter: Smokey Ardisson (offline for a while; not following bugs - do not email), Unassigned)


Dependency tree / graph


After testing Max's bmo customizations to enhance text field (keywords, URL, etc) widths and fluid sizing in bug 452824, I commented:


This is far, far better than before! Thanks, Max!

One thing I noticed, though, is that what happens on the right side/edge varies
when you expand your window width. Compare


In the final bug, you get a much better layout in the right column as you
expand the width of your window (mine starts at 867px, for purposes of
comparison).  In the first two bugs, people with larger window widths don't get
much extra room for status and url and so forth because Boris's "name" unwraps
and expands to fill the space (as does the space between the flag name and the
flag <select> in the second one).  In both of the first two bugs, the
whitespace on the right edge is 50% larger than in the third bug.

As I said before, this is *much* better than before, both in initial size and
in "expandability"; I don't know if these other issues can be optimized away,
but I did want to mention them (I'm happy to move them to another bug if
warranted, too).


Max responded: 


Yeah, that's a good standard problem with tables. We could set a width on the
second column, I don't think that'd hurt anything. You should probably file
another bug for it, upstream.


Comment 1

10 years ago
Yeah, particularly after bug 464187 goes in, we'll want this. The main idea here is that the right column should wrap. It may need a percentage or fixed width.
Severity: normal → enhancement
Depends on: 464187
Priority: -- → P2
Target Milestone: --- → Bugzilla 3.4


10 years ago
Blocks: 465690


10 years ago
No longer blocks: 465690

Comment 2

9 years ago
too late for 3.4.
Target Milestone: Bugzilla 3.4 → Bugzilla 4.0


6 years ago
Depends on: 662605

Comment 3

6 years ago
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0


4 years ago
Target Milestone: Bugzilla 5.0 → ---
You need to log in before you can comment on or make changes to this bug.