Closed
Bug 440628
Opened 16 years ago
Closed 15 years ago
KB article: Multi-touch does not work
Categories
(support.mozilla.org :: Knowledge Base Articles, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jason.barnabe, Assigned: bbayles)
References
()
Details
http://support.mozilla.com/tiki-view_forum_thread.php?forumId=1&comments_parentId=72690 http://support.mozilla.com/tiki-view_forum_thread.php?forumId=1&comments_parentId=69053 http://support.mozilla.com/tiki-view_forum_thread.php?forumId=1&comments_parentId=35606 http://support.mozilla.com/tiki-view_forum_thread.php?comments_parentId=75512&forumId=1 I don't even know what multi-touch is...
It's the crazy multiple-finger touchpad thing on new Apple notebooks. http://discussions.apple.com/thread.jspa?threadID=1467992 looks promising.
Sorry for the bugspam, found something better: MultiClutch appears to work - http://wcrawford.org/2008/02/28/everytime-i-think-about-you-i-touch-my-cell/ I don't know if we want to link to that in an article, though.
Comment 3•15 years ago
|
||
Firefox 3.5 supports this. We can create an article that tells users to 3.0 doesn't support, but 3.5 does so upgrade now!
I put up a really sparse draft. For FF3.5 users, I put a generic note about updating drivers. I don't think it will be that useful, but how else to handle people whose multi-touch doesn't work in FF3.5? This will be a bigger deal when Windows 7 is released.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 5•15 years ago
|
||
Renaming bug. I like your title better. :-)
Summary: KB article: Multi-touch doesn't work with Firefox 3 → KB article: Multi-touch does not work
Comment 6•15 years ago
|
||
Moved to KB at: Wed 14 of Oct, 2009 18:04 EST I think the note about upgrading can be applied to all versions. I haven't heard of multi-touch not working on 3.5; so it may be better to consider this a 3.0-only article until we see cases of multi-touch not working.
Status: RESOLVED → VERIFIED
Updated•15 years ago
|
Assignee: nobody → bbayles
You need to log in
before you can comment on or make changes to this bug.
Description
•