Closed Bug 714605 Opened 14 years ago Closed 2 years ago

[10.7] Support two-finger horizontal swipe on OS X Lion, 32-bit mode

Categories

(Core :: Widget: Cocoa, defect)

x86_64
macOS
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: alex.bock, Unassigned)

References

Details

Cannot use two finger swipe gesture when Nightly is set to "Open in 32 Bit". Blocks 668953.
Blocks: 668953
Component: General → Widget: Cocoa
Product: Firefox → Core
QA Contact: general → cocoa
Hardware: x86 → x86_64
Summary: [10.7] Support two-finger horizontal swipe on OSX Lion (32 bit) → [10.7] Support two-finger horizontal swipe on OS X Lion, 32-bit mode
It'd be interesting to see if this happens on a machine that's native 32-bit, too. I'm not sure if any of those support Lion, however.
> Cannot use two finger swipe gesture when Nightly is set to "Open in 32 Bit". This was intentional. See bug 668953 comment #67. We won't be able to fix this bug until we drop support for OS X Leopard (10.5).
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to Steven Michaud from comment #2) > > Cannot use two finger swipe gesture when Nightly is set to "Open in 32 Bit". > > This was intentional. See bug 668953 comment #67. > > We won't be able to fix this bug until we drop support for OS X Leopard Do we even want to? Is there a really good reason to be running an application in 32-bit mode *other* than to support some ancient plug-in? That's the only use-case I can think of off the top of my head, and it seems like it might be enough of an edge case at this point that those people could just be told "keep an old version of Firefox around". If this is really easy to fix, however, then yeah, it's probably worth it. That wasn't the impression I got from your comment in the other bug, though.
Once we drop support for OS X 10.5 the fix will be trivial -- just drop the #ifdef __LP64__ blocks around the relevant code :-)
Severity: normal → S3

10.7 is no longer supported.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.