Start mozilla. If the default page didn't load (which it doesn't for me), load a page. Notice the scrollbar draws but the thumbs don't until you click on the area where they should be.
I didn't see this in today's verfication builds. What build are you using? Why did you mark this critical severity? That's reserved for crash, data loss and severe leaks. Since there is a workaround, this isn't even major severity.
Don't see this in today's verification build either, nor in a debug build of the tip from 2 hours ago.resolving as wfm, if you still see it please reopen with sufficient information to reproduce.
This seems to work fine if you start with the sidebar *open*, and a URL such as Tinderbox loads in the sidebar. If you launch with the sidebar closed, then I see what syd sees. So to reproduce: 1. Create a new profile and launch that profile. 2. Click on grippy to close sidebar (note that default home page does not load) 3. Shutdown and relaunch (still no default home page) 4. Click on bugzilla personal toolbar link (or any other). Results: no arrows on scrollbars This happens whether the sidebar is minimized (by using the grippy) or completely off, by use View - Sidebar. Re-opening and marking beta1, but I'm thinking this might go away once the default open page problem is fixed, bug 26959. But then the problem will still occur for people who start with about:blank as their home page. Of course, I could be completely wrong.
I still don't see this, and have been launching with the sidebar closed, also tried collapsed. I tried it with about:blank as my default page (app froze trying to create new profile.) With about:blank I get no page, hence no scrollbars at all. Once I load any page, I have complete scrollbars, both thumbs and arrows. Does it really require a new profile? If so, how are you making one today?
We get this pretty regularly in the commercial tree, with IM definitely.
I'm using mozilla, not commercial build, which launches okay. to make a new profile, I just do a rm -fr ~/.mozilla then launch and I'm forced into it, but I don't know if that is a guaranteed way of reproducing this bug
I'll give this to evaughan, but I still can't reproduce it. We need more info in the bug report.
Mass-moving most M15 bugs to M16
reducing severity to normal.
spam, open xptoolkit qa contact moving over to jrgm
I can't reproduce this at all on a linux build for today (and I see that it's been a while since any one has positively seen it). Marking WORKSFORME, but ... reopen if there is a reproducible, etc., etc. ...
Works for me: Platform: PC OS: Redhat 6.2 Linux 2.2.14 Mozilla Build: 2000103108 M18 Trunk Build Marking as verified.