Closed
Bug 313816
Opened 19 years ago
Closed 18 years ago
Hard to read top 100 bug descriptions in Step 1 of reporting a bug
Categories
(Bugzilla :: Query/Bug List, defect, P3)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.22
People
(Reporter: dick, Assigned: gerv)
References
Details
Attachments
(1 file, 1 obsolete file)
772 bytes,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 The Top 100 window is very short, vertically, so it is hard to read the content of a truly popular bug. Perhaps when you actually select such a bug to read, you could get a WHOLE PAGE of the content rather than three or four lines at a time. Since it is a Top 100 bug report, you may be suspicious that the contents are looooong and give it some room to stretch out and relax. Reproducible: Always Steps to Reproduce: 1.Pick the second bug in Top 100. 2.Read the contents, very slowly and painfully 3.Write that up as a bug. That's what I'm doing. Actual Results: hard to read Expected Results: easy to read switched to a much larger window so more can be seen before needing to scroll more.
Comment 1•19 years ago
|
||
*** Bug 315094 has been marked as a duplicate of this bug. ***
Updated•19 years ago
|
Assignee: query-and-buglist → justdave
Blocks: bmo-upgrade-051022
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: MacOS X → All
Priority: -- → P3
Hardware: Macintosh → All
Version: unspecified → 2.20
Updated•19 years ago
|
Assignee: justdave → query-and-buglist
Comment 2•18 years ago
|
||
Gerv owns this page
Assignee: query-and-buglist → gerv
No longer blocks: bmo-upgrade-051022
Assignee | ||
Comment 3•18 years ago
|
||
The HTML says that the <iframe> should be 80% of the height of the viewport, but Firefox is ignoring this and using the default height. This behaviour is rendering-mode dependent, and it changed when mkanat added a system identifier to our DOCTYPE in March 2005 in bug 162194. This switched us from Quirks mode to Almost-Standards mode. We have the following choices: - Change the page to use a fixed pixel height for the <iframe> - Find a way to change this template only to have a different doctype, probably by inserting it above [% PROCESS global/header.html.tmpl %] - Reverse bug 162194 Gerv
Comment 4•18 years ago
|
||
Wow, the Standards Modes don't allow us to use % heights on an <iframe>? (I think we already have this bug filed somewhere, by the way.) I think the best way to go is a fixed-pixel height for the <iframe>.
Assignee | ||
Comment 5•18 years ago
|
||
Let's go with that, then. Gerv
Attachment #229228 -
Flags: review?(mkanat)
Assignee | ||
Updated•18 years ago
|
Severity: enhancement → minor
Status: NEW → ASSIGNED
Target Milestone: --- → Bugzilla 2.24
Comment 6•18 years ago
|
||
Hmmm... Is this a browser bug? http://www.w3.org/TR/html4/present/frames.html#h-16.5 tells me iframe height values may well be percentages: the height attribute should be a "length" (http://www.w3.org/TR/html4/types.html#type-length).
Assignee | ||
Comment 7•18 years ago
|
||
I'm not sure; there are a few bugs which discuss the subject, and one makes the point that it's hard to calculate a percentage height if the containing block doesn't have a specific height of its own. When should the percentage refer to the height of the container, and when to the height of the viewport? CCing roc to see if he can add any clarity. Gerv
#container is height:auto so its %-height children don't work. Try making it height:100%. You might also need height:100% on BODY and HTML. They will overflow vertically anyway so it shouldn't hork the page.
Assignee | ||
Comment 9•18 years ago
|
||
Ah, nice one. That'll do. This also fixes the problem, but still uses percentages.
Attachment #229228 -
Attachment is obsolete: true
Attachment #229234 -
Flags: review?(mkanat)
Attachment #229228 -
Flags: review?(mkanat)
Comment 10•18 years ago
|
||
Comment on attachment 229234 [details] [diff] [review] Patch v.2 Okay. I trust Roc. :-)
Attachment #229234 -
Flags: review?(mkanat) → review+
Comment 11•18 years ago
|
||
I don't see anything wrong with backporting this. It's a template change, but an extremely minor one, on a page that is probably only rarely used in translations.
Flags: approval?
Flags: approval2.22?
Flags: approval2.20?
Target Milestone: Bugzilla 2.24 → Bugzilla 2.20
Comment 12•18 years ago
|
||
I can see 2.22, which is our most recent stable release, but does this really need to go into 2.20?
Flags: approval?
Flags: approval2.22?
Flags: approval2.22+
Flags: approval+
Comment 13•18 years ago
|
||
No, I would suppose it doesn't. :-) I'd imagine justdave might want to apply it to bmo, though.
Flags: approval2.20?
Updated•18 years ago
|
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Comment 14•18 years ago
|
||
gerv, too lazy to commit your patch yourself? :-p
Assignee | ||
Comment 15•18 years ago
|
||
No, just snowed under with stuff. I'll get to it :-) Gerv
Assignee | ||
Comment 16•18 years ago
|
||
Checked in on trunk and 2.22 branch. Trunk: Checking in template/en/default/bug/create/create-guided.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/bug/create/create-guided.html.tmpl,v <-- create-guided.html.tmpl new revision: 1.34; previous revision: 1.33 done Branch: Checking in template/en/default/bug/create/create-guided.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/bug/create/create-guided.html.tmpl,v <-- create-guided.html.tmpl new revision: 1.26.4.4; previous revision: 1.26.4.3 done Gerv
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 17•18 years ago
|
||
*** Bug 354860 has been marked as a duplicate of this bug. ***
Comment 18•18 years ago
|
||
*** Bug 321689 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•