Erratic touchpad behavior in Thunderbird version 38.2.0
I'm running Windows 10 on a Lenovo Yoga 3 laptop. The touchpad uses the Lenova Yoga Windows 10 driver from Elan. Microsoft update loaded a newer driver dated July 2015. My problem is that Thunderbird cannot track where the mouse is in the application. If I click on a message and then move the mouse down to the message body and try to scroll down though the message, instead of scrolling through the message body, Thunderbird will scroll down through the messages in the inbox. If i click in the message body, then Thunderbird knows where the mouse is and will then scroll down the message body, but the scrolling is so fast that you cannot control it. If I move the mouse back up to the inbox and try to scroll down though the emails, Thunderbird still thinks the mouse is in the message body and will continue to scroll there. If I click on a message in the inbox, then Thunderbird will know where the mouse is and will then scroll down through the inbox message, however, the scrolling is so fast that it will scroll down past over 5,000 messages to the end of the inbox. Just tying to understand why this is happening and if there is anything I can do to fix it? I've uninstalled and reinstalled Thunderbird but the mouse behavior is still the same. No other application on the laptop is displaying this mouse behavior, including Firefox. Thoughts?
ყველა პასუხი (3)
That sounds like a mouse driver issue to me.
I agree, but Lenovo tech support thinks it's an app issue. It is strange though that the only app displaying the issue is Thunderbird.
Yes and no. Thunderbird uses XUL, not standard "windows" Sometime issues appear in XUL that do not appear in standard windows. They may however appear in OSX or Linux. Mozilla however are in the process of depricating XUL so are most unlikely to fix anything that does not affect Firefox.
Two things do appear to be common, almost all mouse issues I have seen over the past 4 or 5 years Lenovo, and flat batteries. My personal guess is they somehow deviate from the Windows spec in their implementations.