...Anyone? I noticed today that my computer at work (also brand new) has no issues scrolling inside the drop down menus using the mouse scroll wheel. This narrows it down to the computer itself, and or the track pad vs mouse.

Still wondering...

• Jeopardy theme plays*

The mystery continues...

Really? No one?

To the top...

• crickets chirping*

Try to modify the ui.trackpoint_hack.enabled pref on the about:config page from the default value -1 to 0 or 1 to see if that makes the scroll pad work better.

Close and restart Firefox after changing the ui.trackpoint_hack.enabled pref.

• http://kb.mozillazine.org/about:config

Thank you for the suggestion, however it did not change anything at either setting.

Any other ideas out there?

Did I see someone raise their hand with a suggestion? Oh, guess not...

Bump...

To the top.

Still isn't working. Other laptops new in the store have the same issue. What gives?

Still wondering...

Are you running Firefox 12 now with the same result?

I don't have an HP or a Windows 7 laptop, but I can test on a Dell running XP (for what that's worth).

Can you supply a link to a page that has this problem and describe the steps to recreate it. Where is the mouse pointer when you're trying to scroll?

Yes I am running Firefox 12.

Go to this link: http://sacramento.craigslist.org/sss/

Click the drop down for the category. Use the track pad to scroll the list. Mine closes the list and returns focus to the browser instead of scrolling the list. This works fine in IE.

The mouse pointer typically is inside the drop down when attempted, but it doesn't work inside, outside, or directly on top of the scroll bar.

As I said, it's odd because the focus follows the pointer to scroll other things like texts boxes and stuff just fine (like the one I am using now). Pointer inside the box, the box scrolls, pointer outside, and the window scrolls.

I tried a Dell Latitude D630 running Windows XP and it seemed to scroll normally (as long as I kept my finger far enough right on the touchpad). It has an Alps Electric touchpad with a driver dating back to Feb. 2007. This may not be comparable to what you have on your HP. Do you know which kind you have (e.g., Alps, Synaptics)? You could try the Mouse Control Panel for information, or perhaps there is a separate one for the touchpad.

It's Synaptics Touch Pad v8.1. It is using a driver provided by Synaptics, version 15.3.29.0 dated 10/13/2011, and is supposedly the most current version. I have tried getting newer off the HP website, letting Windows search for the most current version, and looking at the Synaptics site, but I still end up with the same version.

I have double checked the scrolling regions to make sure I am within them as well as all the other settings regarding the touch pad. In fact, I had to enable the scrolling regions because they were disabled by default and instead used two finger scrolling. For what it's worth, two finger scrolling gives me the same result - it does not scroll the drop down menu.

As I said, it works just fine in IE and all other programs, so I'm not sure I understand how the drivers for the touchpad could be the issue. It seems to me it's more likely that Firefox is not interpreting the "signal" from the touchpad correctly, yet IE does. Then again, I've been wrong before...

Oh, I also tried adding the "UseScrollCursor" DWORD to the registry which seemed to solve issues for other people when using Synaptics and Firefox, did not help my situation. It removed the scrolling icon like it was supposed to, but the drop down menus still do not scroll.

I had this exact problem, same HP specs and Synaptics driver. I went to synaptics site and downloaded their latest driver which is lower than 15.3.29.0 for some reason. It's 15.2.20, I got the one for 64 bit since that's what I have. You have to uninstall the 15.3.29.0 first since it's "newer". Now it works like it should in FF as well as IE and everything else. So for some reason the latest FF does have a clash with the latest synaptics driver and the FF devs need to include a fix with the next update.