Closed
Bug 391740
Opened 17 years ago
Closed 17 years ago
listheader in richlistbox appears to right/at bottom of richlistitems
Categories
(Toolkit :: UI Widgets, defect)
Toolkit
UI Widgets
Tracking
()
VERIFIED
FIXED
mozilla1.9beta1
People
(Reporter: myk, Assigned: philip.chee)
References
Details
Attachments
(5 files, 1 obsolete file)
In bug 376815, mano added support for using listheader in richlistboxes. But when I try it, listheader appears to the right of the richlistitems in the richlistbox, not on top, as I would expect. And orienting the richlistbox vertically also doesn't fix the problem. It causes the listheader to appear at the bottom, not at the top. Here's a testcase that demonstrates the problem. Might this be fixed by bug 367843?
Comment 2•17 years ago
|
||
Found the cause.
Comment 3•17 years ago
|
||
(In reply to comment #2) > Created an attachment (id=280161) [details] > Patch > > Found the cause. I tried this patch. It looks good.
Comment 4•17 years ago
|
||
Comment on attachment 280161 [details] [diff] [review] Patch r=mano
Attachment #280161 -
Flags: review?(mano) → review+
Comment 5•17 years ago
|
||
Comment on attachment 280161 [details] [diff] [review] Patch Let's try for M8 approval. My reasoning is that this will at least prevent the inevitable bug reports from M8 users about this issue, and the fix is one line long.
Attachment #280161 -
Flags: approval1.9?
Updated•17 years ago
|
Target Milestone: --- → mozilla1.9 M8
Comment 6•17 years ago
|
||
I found there were two more problems. 1. Scroll with column header. Column header should stay the position. 2. The height of the last row is too narrow. Should I open new bug?
with below tip in userChrome.css #handlersView { -moz-box-direction: reverse; } no problem with scroll, header stays at the top. but last line is cut off.
another tip, #handlersView > listheader { -moz-box-ordinal-group: 1; }
Comment 9•17 years ago
|
||
Comment on attachment 280161 [details] [diff] [review] Patch a=bzbarsky
Attachment #280161 -
Flags: approval1.9? → approval1.9+
Updated•17 years ago
|
Keywords: checkin-needed
Reporter | ||
Comment 10•17 years ago
|
||
Thanks for the patch! I have checked it in. Checking in toolkit/content/widgets/richlistbox.xml; /cvsroot/mozilla/toolkit/content/widgets/richlistbox.xml,v <-- richlistbox.xml new revision: 1.44; previous revision: 1.43 done (In reply to comment #6) > I found there were two more problems. > 1. Scroll with column header. > Column header should stay the position. > 2. The height of the last row is too narrow. > > Should I open new bug? Yes, please do open new bugs for these issues.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Keywords: checkin-needed
OS: Linux → All
Hardware: PC → All
Resolution: --- → FIXED
Comment 11•17 years ago
|
||
> 2. The height of the last row is too narrow.
no problem with Win XP default theme.
Comment 12•17 years ago
|
||
(In reply to comment #11) > Created an attachment (id=281272) [details] > screen shot > > > 2. The height of the last row is too narrow. > > no problem with Win XP default theme. Worksforme too with today's build. Sorry I don't know why. Anyway I opened bug 396545 for first problem.
Comment 13•17 years ago
|
||
Note: Some people are reporting that the headers are still appearing at the bottom of the list. Littlemutt has discovered that this happens if you have Console² extension installed. Just a headsup.
Assignee | ||
Comment 14•17 years ago
|
||
I plan to update Console² in the next few days.
Comment 15•17 years ago
|
||
I don't think this patch really fixed this problem. Adding xul:listheader to the includes statement just makes it NOT match the listheaders (I don't think xbl bindings are that smart about namespaces... or anything really except nodeNames), so they're pushed into the box and Bug 396545 happens. The reason they're being put at the bottom of the box is because the single listheader element being used here contains some treecols, which get displayed strangely because of the way the tree box model fits things. An easier fix than that is to just make the richlistbox take a listhead element instead of a listheader element, and then put two listheaders inside of it. Doing so here seemed to make everything work and look fine (minus some theme problems), but I don't have the means to write a diff, and I'm not sure if the listheader/treecol decisions were made for some better reason.
Reporter | ||
Comment 16•17 years ago
|
||
Sounds like this needs a better fix.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•17 years ago
|
Attachment #280161 -
Attachment is obsolete: true
Comment 17•17 years ago
|
||
In fact, the fix should be backed out.
Assignee | ||
Comment 18•17 years ago
|
||
http://lxr.mozilla.org/seamonkey/source/toolkit/content/xul.css#445 listheader { -moz-binding: url("chrome://global/content/bindings/listbox.xml#listheader"); -moz-box-ordinal-group: 2147483646; } This was introduced in Bug 178604 which is why the listheader appear at the bottom.
Assignee | ||
Comment 19•17 years ago
|
||
This patch fixes the test case in this bug and it doesn't cause the listheader in a richlistbox to scroll, but it might affect consumers of <richlistbox> that assume that the default orientation is horizontal.
Assignee | ||
Comment 20•17 years ago
|
||
Comment on attachment 281843 [details] [diff] [review] Proposed patch > but it might affect consumers of <richlistbox> that > assume that the default orientation is horizontal. Actually prior to the listheader support, all children ended up in a vertical scrollbox anyway so I don't think that there are any usages that depend on a richlistbox being horizontally inclined.
Attachment #281843 -
Flags: review?(mano)
Assignee | ||
Comment 21•17 years ago
|
||
Um I forgot to mention that the first patch has to be backed out first.
Updated•17 years ago
|
Assignee: ventnor.bugzilla → philip.chee
Status: REOPENED → NEW
Updated•17 years ago
|
Flags: blocking1.9? → blocking1.9+
Comment 22•17 years ago
|
||
Comment on attachment 281843 [details] [diff] [review] Proposed patch r=mano, many thanks.
Attachment #281843 -
Flags: review?(mano) → review+
Updated•17 years ago
|
Keywords: checkin-needed
Whiteboard: old patch needs to be backed out
Target Milestone: mozilla1.9 M8 → mozilla1.9 M9
Version: unspecified → Trunk
Reporter | ||
Comment 23•17 years ago
|
||
Comment on attachment 281843 [details] [diff] [review] Proposed patch Requesting approval to revert the previous patch and check in this one. This patch is the correct fix for the problem. It's a polish fix for the Applications prefpane, and it shouldn't cause problems for other richlistboxes, as they too are vertically oriented, and none of them use listheaders.
Attachment #281843 -
Flags: approval1.9?
Comment 24•17 years ago
|
||
This bug has been marked as blocking.
Reporter | ||
Comment 25•17 years ago
|
||
Comment on attachment 281843 [details] [diff] [review] Proposed patch (In reply to comment #24) > This bug has been marked as blocking. Ah, indeed. In that case canceling approval request. I'll check this in.
Attachment #281843 -
Flags: approval1.9?
Reporter | ||
Comment 26•17 years ago
|
||
I have reverted the original patch: Checking in toolkit/content/widgets/richlistbox.xml; /cvsroot/mozilla/toolkit/content/widgets/richlistbox.xml,v <-- richlistbox.xml new revision: 1.45; previous revision: 1.44 done I haven't yet checked in the new patch, however, because of the following message at the top of toolkit/content/xul.css: THIS FILE IS LOCKED DOWN. YOU ARE NOT ALLOWED TO MODIFY IT WITHOUT FIRST HAVING YOUR CHANGES REVIEWED BY mconnor@steelgryphon.com
Whiteboard: old patch needs to be backed out
Reporter | ||
Updated•17 years ago
|
Attachment #281843 -
Flags: review?(mconnor)
Updated•17 years ago
|
Keywords: checkin-needed
Comment 28•17 years ago
|
||
Comment on attachment 281843 [details] [diff] [review] Proposed patch mconnor gave this r+ over IRC. I'll land it now.
Attachment #281843 -
Flags: review?(mconnor)
Comment 29•17 years ago
|
||
Checking in toolkit/content/xul.css; /cvsroot/mozilla/toolkit/content/xul.css,v <-- xul.css new revision: 1.104; previous revision: 1.103 done
Status: NEW → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Comment 30•17 years ago
|
||
Verified fixed in Minefield/3.0a9pre ID:2007101214
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•