Closed
Bug 55899
Opened 24 years ago
Closed 24 years ago
ftp and file picker columns get out of synch when scrolling or opening folders
Categories
(Core Graveyard :: Skinability, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: eric, Assigned: eric)
References
()
Details
(Whiteboard: [rtm++] CHECKED IN ON TRUNK and BRANCH-modern/blue)
Attachments
(1 file)
4.66 KB,
patch
|
Details | Diff | Splinter Review |
To repoduce: 1) open the browser and go to ftp://ftp.mozilla.org 2) Open a bunch of directories 3) Scroll up and down Then columns don't line up with the contents. They are just scattered all over the place. To reproduce in file picker 1) One unix select open file 2) Scroll up and down the columns will not align This is high visibility and I already have a simple CSS fix. Attached is the patch. This fix is a simple 9 line change directory.css. (Directory in in 4 places. That's why the patch looks redundant.)
Assignee | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
rtm need info: this minimal css fix has already been done for thread pane, would be good to get it in for FTP if possible. Probably best to test on trunk first.
Comment 3•24 years ago
|
||
a=hyatt
Comment 4•24 years ago
|
||
r=ben
Comment 5•24 years ago
|
||
Why isn't this marked rtm+? It seems like it was ready a day ago. Has it been thoroughly tested? cc self, jrgm
Comment 6•24 years ago
|
||
This was checked into the trunk Monday afternoon. In this evening's trunk builds, mac/linux/win32, this is working well and reliably so. It fixes the scroll problem in both ftp:// and file:// listings of directory.xul (and improves the default column sizing as a bonus!). No regressions noted. So, with r=ben, a=hyatt, tested on trunk on three platforms, marking [rtm+] for PDT approval.
Whiteboard: [rtm need info] → [rtm+] CHECKED IN ON TRUNK
Assignee | ||
Comment 7•24 years ago
|
||
This fix is extremely simple. Its a little CSS that is only invoked when ftp is hit of the file picker is hit. It is VERY LOW risk in my opinion.
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•24 years ago
|
||
Fixed in branch.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 10•24 years ago
|
||
blake - can I assign this to someone to verify on the branch since jrgm has verified on the trunk?
Whiteboard: [rtm++] CHECKED IN ON TRUNK → [rtm++] CHECKED IN ON TRUNK and BRANCH
Comment 11•24 years ago
|
||
I regularly build the branch...I'll verify this asap tomorrow, since I find that 2:30 am isn't optimal time for verifications ;)
Comment 12•24 years ago
|
||
vrfy fixed in new win2k trunk build, but NOT working in new win2k branch build. I also just filed related bug 58346 which doesn't work in either the branch or trunk, but that'll probably require a different fix (it's not a directory structured tree). Why is this bug in skinability, anyways?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•24 years ago
|
||
If I didn't know better, I would say that something was up with CVS. I "saw" these checkins to the branch, and had already checked that it was working for branch builds in both skins. But now, it says that this checkin to directory.css never happened for the classic skin. (It does work in the modern skin).
Comment 14•24 years ago
|
||
That's strange. I'll cc: leaf and granrose in case they know what may be happening. This is reopened and the branch is closed for checkins until Monday. I will change the rtm++ to rtm+ for re-evaluation for candidate limbo on Monday morning.
Whiteboard: [rtm++] CHECKED IN ON TRUNK and BRANCH → [rtm+] CHECKED IN ON TRUNK and BRANCH
Comment 15•24 years ago
|
||
Sorry. I should have been clearer. I don't really think CVS magically reverted this change. (I just have such a clear, but erroneous, recollection that I had seen this checkin on the branch that I am stunned to see that that is not the case.)
Whiteboard: [rtm+] CHECKED IN ON TRUNK and BRANCH → [rtm+] CHECKED IN ON TRUNK and BRANCH-modern/blue
Comment 16•24 years ago
|
||
PDT marking [rtm++]. This bug is now out of limbo and approved for checkin to the branch. Please check in ASAP.
Whiteboard: [rtm+] CHECKED IN ON TRUNK and BRANCH-modern/blue → [rtm++] CHECKED IN ON TRUNK and BRANCH-modern/blue
Assignee | ||
Comment 17•24 years ago
|
||
Why was this bug reopened? The fix is in the branch and trunk. Bug 58346 is a DIFFERENT bug. The fix is not in the tree code but the XUL that describes the tree. You MUST give each column a width.
Comment 18•24 years ago
|
||
Eric, I reopened this because it still doesn't work for me in a branch build. Can anyone confirm or deny this? I realize that 58346 will require a different fix; I said that earlier.
Comment 19•24 years ago
|
||
Eric, the classic skin directory.css does not include the patch to set the width: for the treecols. (As I said earlier, I am puzzled as to where this patch went, because I was sure I saw it go into the branch, but ... check the URL on this bug. I can also confirm the columns get out-of-synch when using 10/29 win32 Classic skin).
Comment 21•24 years ago
|
||
Yes, classic-only. Sorry, should have mentioned that... and that's very strange wrt the patch already having gone in.
Assignee | ||
Updated•24 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 22•24 years ago
|
||
fixed
Comment 23•24 years ago
|
||
blake - can you verify this in the branch builds again?
Comment 24•24 years ago
|
||
verified on the branch 11/01 mac/linux/win32 builds (really this time). (and blake has verified trunk previously comments above). (Side-note: I think blue on the trunk doesn't have this css change, but that's outside the scope of this bug, and I don't know if there is really any support for maintaining blue going forward).
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•