Closed Bug 459458 Opened 16 years ago Closed 16 years ago

Google Docs spreadsheets menu item (save and close) doesn't work in Camino

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 404433

People

(Reporter: nep, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.17) Gecko/20080915 Camino/1.6.4 (like Firefox/2.0.0.17) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.17) Gecko/20080915 Camino/1.6.4 (like Firefox/2.0.0.17) Google Docs just introduced new menus for their spreadsheet app. The menus do not work in Camino -- they drop down, but clicks do not activate the functionality (they just cause the menus to disappear again) Reproducible: Always Steps to Reproduce: 1. Go to Google Docs 2. Start a new spreadsheet 3. Try to run a menu command in the new spreadsheet Actual Results: Nothin' Expected Results: The command should be triggered.
Summary: Google Docs spreadsheets menus don't work in Camino → Google Docs spreadsheets menu item (save and close) doesn't work in Camino
I retested, and apologize -- specifically, the Save and Close command does not work.
1.6 has issues with some of the more complex toolbars in Google apps, but it works correctly in the trunk builds that will become 2.0, so closing WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
This is fixed in Camino 2.0a1pre builds. If you don't want to use the 2.0a1pre builds, you can make almost all Google Docs menu items function in release builds by using the arrow keys to highlight menu items and return to select them. If you do want to try 2.0a1pre builds, be sure to make a backup copy of your profile folder (~/Library/Application Support/Camino) first, since you won't be able to use your profile with 1.6.x after launching a 2.0a1pre.
Resolution: WORKSFORME → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.