Closed Bug 554237 Opened 15 years ago Closed 15 years ago

Dual vertical scrollbars if any type of add-ons exceed window area

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.9.3a5

People

(Reporter: tchung, Assigned: mossop)

References

Details

(Whiteboard: [rewrite])

Attachments

(4 files)

Attached image Dual Sliders Screenshot
Dual vertical sliders appear if installed extensions exceed the window area of addons. See screenshot. A new instance of Addons Manager is opened whenever your reloading a disabled plugin. Instead, it should just detect the addons manager tab is already opened, and navigate to it. Repro: 1) Download Addons project branch nightly: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a4pre) Gecko/20100321 Minefield/3.7a4pre 2) install a few extensions 3) Resize the firefox window so it forces the extension list too long that you need to pan down 4) Verify dual sliders appear Expected: - single vertical sliders Actual: - dual vertical sliders
Blocks: 550048
Keywords: uiwanted
Whiteboard: [rewrite]
It's something simple Blair can fix. No input from ux needed here.
Keywords: uiwanted
Grr, another mac-only bug.
Went to find this on the Mac build, assuming it was Mac-only, since I never saw it on Windows - but I can't reproduce it on Mac either. It could potentially have been introduced by http://hg.mozilla.org/projects/addonsmgr/rev/035f20067079 But I don't see anything that would have accidently fixed this in the past couple of days. Can you verify with a newer build?
I can see this on Windows too. In my case it is visible on the themes pane after installing the Waltnut theme. The innermost scrollbar has the height of all theme richlist entries while the outer one is for the panes.
Summary: Dual vertical sliders if extensions exceed window area → Dual vertical scrollbars if extensions exceed window area
I see this on extensions, but not plugins.
Summary: Dual vertical scrollbars if extensions exceed window area → Dual vertical scrollbars if any type of add-ons exceed window area
First guess: Maybe you need an addon with a multi-line description. Line-wrapping is known to cause headaches in XUL. Why are there nested scrollboxes in the first place?
Oh I see, the changeset you linked to... Does this work? #search-list > scrollbox { overflow: visible; } Though it would probably be cleaner to create non-scrolling-richlistbox binding that doesn't use a <scrollbox>.
Blocks: 562952
Bug on windows Confirmed
Blocks: 562944
Blocks: 562885
(In reply to comment #9) > Oh I see, the changeset you linked to... > > Does this work? #search-list > scrollbox { overflow: visible; } > > Though it would probably be cleaner to create non-scrolling-richlistbox binding > that doesn't use a <scrollbox>. Note to self: This fixes it.
(In reply to comment #9) > Though it would probably be cleaner to create non-scrolling-richlistbox binding > that doesn't use a <scrollbox>. Why do you need a non-scrolling-richlistbox anyway?
(In reply to comment #14) > (In reply to comment #9) > > Though it would probably be cleaner to create non-scrolling-richlistbox binding > > that doesn't use a <scrollbox>. > Why do you need a non-scrolling-richlistbox anyway? Because there are other things we want to scroll with the addon items, but shouldn't act like a richlistitem (such as the search filter checkboxes).
Why make it yourself so hard in wanting to also scroll the filter checkboxes? The richlistitem itself has scrolling implemented, re-implementing it will cause another series of bugs to be solved... (dual scrollbars, scroll to selected item, etc). With normal trees, the sort-direction in the treecol also doesn't scroll away... Also, when the search filter checkboxes are scrolled away, will also cause usability issues...
(In reply to comment #3) > Went to find this on the Mac build, assuming it was Mac-only, since I never saw > it on Windows - but I can't reproduce it on Mac either. > > It could potentially have been introduced by > http://hg.mozilla.org/projects/addonsmgr/rev/035f20067079 > > But I don't see anything that would have accidently fixed this in the past > couple of days. Can you verify with a newer build? I noticed its in the new landing, but only came across it when I made the browser 1/4 the screen size of 1024x768.. it shows both scrollbars in the right hand side, but if the browser takes up the entire screen and the list is still scrollable, I only get one vertical scrollbar. I'm on Windows 7.
Just to re-confirm that this is still happening.
Thanks... just so everyone knows, until this bug is fixed it will continue to happen so no need to confirm / re-confirm.
FYI-I just found that installing FlashGot causes this for me. Uninstalling "corrected" things. Disabling had no effect. So long as FlashGot was installed, there appeared to be the extraneous scroll bar. I will attach a picture of the Add-on Mgr with FlashGot, Java Quick Starter and Java Console as the only installed add-ons. You will be able to see the scroll bar on the right even though there is not enough installed add-ons to trigger the normal window scroll bar.
FYI-Without FlashGot installed, my nearly 30 installed add-ons installed on a new profile produces the expected normal scroll bar.
This bug seem to be triggered if any of the extensions have an extensive description. When I shortened the description for FlashGot and NoScript (the two extension that had long descriptions) the extra scrollbar disappeared.
I had the Add-on Mgr. in a maximized browser tab. Later when I windowed the browser, the second scroll bar would appear. Maximizing it again did not remove the added scroll bar.
Attached patch patch rev 1Splinter Review
Using nested scrollboxes is going to leave us implementing workarounds for all the stuff that richlistbox already implements itself so I think we should just go for a straight single richlistbox for the list views. The only real annoying part is that the sort service won't ignore the header elements but we can get around that by temporarily removing them from the list when sorting.
Assignee: nobody → dtownsend
Status: NEW → ASSIGNED
Attachment #444796 - Flags: review?(bmcbride)
Comment on attachment 444796 [details] [diff] [review] patch rev 1 This does indeed seem a lot better.
Attachment #444796 - Flags: review?(bmcbride) → review+
Comment on attachment 444796 [details] [diff] [review] patch rev 1 >- this._listBox.collasped = aShow; This isn't theme-friendly... although collasped wasn't either, being a misspelling ;-) Assuming it works, I prefer hidden anyway.
(In reply to comment #27) >(From update of attachment 444796 [details] [diff] [review]) >>- this._listBox.collasped = aShow; >This isn't theme-friendly... although collasped wasn't either, being a >misspelling ;-) Assuming it works, I prefer hidden anyway. Wait, I was looking at the wrong copy of this line (also misspelled).
Landed in http://hg.mozilla.org/mozilla-central/rev/b28ec304976f. Also removed the other broken collasped reference as it clearly wasn't needed.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a5
-> verified
Status: RESOLVED → VERIFIED
Flags: in-testsuite-
Flags: in-litmus-
Fixed :D
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: