Is this a touchscreen desktop pc or portable pc? Could you provide screenshots of the issue? Has this happened in the past? When did this first happen?

Refinement of symptoms: refreshing the page will fix problem for about 5 seconds of scrolling then attempts to scroll, via touch, will just select text. It started a couple weeks ago. I am using a HP touchsmart 610 all-in-one desktop PC.

If you update to 18.0.1, does this issue get resolved?

I got it.

The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information. Note: This will cause you to lose any Extensions, Open websites, and some Preferences.

To Reset Firefox do the following:

1. Go to Firefox > Help > Troubleshooting Information.
2. Click the "Reset Firefox" button.
3. Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
4. Firefox will open with all factory defaults applied.

Further information can be found in the Refresh Firefox - reset add-ons and settings article.

Did this fix your problems? Please report back to us!

I hate doing that (very time consuming) and is it any different than safe mode? check out the pic of my distorted scroll bar using the mouse to click and drag the scroll bar in gmail. The start of this problem may correlate with the latest AMD video card driver update.

Could you provide more details on this if you believe this is due to a video card update? This may be a bug and can be filed.

Not sure the video card driver update is the cause but the problem started around the same time.

Name	ATI Mobility Radeon HD 5570
PNP Device ID	PCI\VEN_1002&DEV_68C7&SUBSYS_22451462&REV_00\4&11B4BF7A&0&0008
Adapter Type	AMD Radeon Graphics Processor (0x68C7), Advanced Micro Devices, Inc. compatible
Adapter Description	ATI Mobility Radeon HD 5570
Adapter RAM	(2,147,483,648) bytes
Installed Drivers	aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver Version	9.10.8.0
INF File	oem37.inf (ati2mtag_Manhattan section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xC0000000-0xCFFFFFFF
Memory Address	0xFE620000-0xFE63FFFF
I/O Port	0x0000E000-0x0000EFFF
IRQ Channel	IRQ 4294967289
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\drivers\atikmpag.sys (8.14.1.6290, 534.00 KB (546,816 bytes), 12/1/2012 11:13 PM)

That information is helpful. You can file you bug here: https://bugzilla.mozilla.org/

This is probably two bugs. I can't say anything considering the strange scrollbar-drawing issue.

The other problem about the behaviour of the scrollbar (jumping around) and the inability to use touchscreen-scrolling like we used to is most probably not related to the graphics card. I have similar issues about the scrolling behaviour on two different windows7-machines since updating to the newest version of firefox. Unfortuntely I can't say which version I have used before (it was an older one though) but before the update touchscreen-scrolling worked. This is most apparent on any google-search-results, but it happens on a few other pages as well.

I have tracked the issue a bit further, and found that disabling JS on those pages and reloading actually restores the old scrolling-behaviour. Of course it also removes any JS-functions, so it is not a good workaround. At least Google will work again, and they have a reasonable JS-less version for display. This indicates some error in JS-handling with firefox in the current version.

Temporary solution: For now I'm using a little addon called "yesscript" to automaticly deactivate JS for pages which malfunction (including google).

you seem to be on the right track. Good work! did you file the bug in bugzilla?

I have indeed filed this as a bug. You can access the report here

I am using Windows 8 on an Asus Vivobook touchscreen laptop with Firefox 19.0.2. I was completely frustrated by this problem until I found ForrestGimp's temporary fix of using YesScript. I am so pleased that at least my Google search results scroll properly with this add-on. Of course, that doesn't help me on sites like WebMD, which require JS for functionality.

Please do something about this incompability! I love my touchscreen laptop (which many, many people have bought in the last few months), and I have been using and loving Firefox for many years. I don't relish the thought of switching to Internet Explorer, but touch scrolling works fine there.

pbonitz: Please ask a new question so we can troubleshoot every user in a better way. Thanks!

It is possible that some of the status keys have the wrong state and Firefox sees them as still pressed.

Try to press all the status keys (Shift, Ctrl, Alt) a few times to see if that helps to recover from this.

feer56: no offence meant, but pbonitz just confirmed the problem is present in the win8-version of FireFox as well, which is valueable information imho.

If anything we could transfer this discussion to https://support.mozilla.org/de/questions/947337?esab=a&s=&r=1&as=s , where the touchscreen-issue is discussed as a single item. In the original post if this thread it's combined with a weird drawing-issue, which is probably not related. But as per my advice, pbonitz has posted there as well (Thanx!).

cor-el: Thank you for the tip. I have tested this, but pressing shift, ctrl and/or alt doesn't help. I tried with both the win7 screen-keyboard and an attached USB-keyboard.

ForrestGimp: Our rules simply state the following: Create one thread and only one thread for each subject you want to discuss. For support requests, do not re-use existing threads started by others, even if they are seemingly on the same subject. You can also find it on this page

I know what you mean, but the intended purpose of that rule can't be to have users open several different threads for one and the same issue, especially when a) the problem, b) the (temporary) solution and c) most assuredly the underlying cause are the same.

However, if that actually was the intention for some reason I'm not aware of, please confirm this and we'll all open our own threads stating this problem individually. I think we all want to make troubleshooting as easy as we can.

Threads often become a "me too" thread which we don't want as some solutions work for some and some don't. We like to troubleshoot each and every case so we have a better understanding of each users issue.

This definitely seems like a javascript thing, and it happens on this site too (for me anyway). I don't get the corrupt scrollbar though so that may be unrelated.