[Mac] [Safari 4] [Snow Leopard] Gears not working Safari 4 - Snow Leopard

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Install the latest seed of Snow Leopard with Safari 4 Beta 
2.Install the latest Gears safari.  
3.Restart safari.

What is the expected output? What do you see instead?
Expected: Gears should work , Safari Menu should have Google Gears Safari
in Safari menu. 

Actual: Gears is listed in installed plugins, but does not show up in the menu.

What version of the product are you using? On what operating system?
Platform:
  Mac OS X Version 10.6 (Build 10A286) - Snow Leopard
  Processor: 4 Intel 2.66 GHz
  RAM: 1024 MB

Gears:
  Gears version: 0.5.15.0

Installed Browsers:
  Safari: 4 Public Beta (6530.1)

Please provide any additional information below.
No errors are reported in the console, gears.google.com does not show Gears
installed after installing.

Original issue reported on code.google.com by gears.te...@gmail.com on 7 Mar 2009 at 2:49

[GoogleCodeExporter]

@47: Are there any plans to update the Google Gears homepage, as it is 
currently misleading. At the moment the 
system requirements are listed as "Mac OS X Leopard 10.5.3+ or Tiger 10.4.11+, 
G4+/Intel CPU" and "Gears is 
available for Windows, Windows Mobile (IE Mobile, Opera Mobile), Mac (Firefox, 
Safari), Linux and Android.", 
which is clearly incorrect as this defect as yet to be addressed, and Gears 
does not have support for Safari or 
Snow Leopard.

Original comment by Immutate on 24 Nov 2009 at 11:10

[GoogleCodeExporter]

This issue must be fixed asap !
I had been using gears a lot, and since I upgraded to snow leopard everything 
stopped work. I'm starting to consider to use thunderbird as mail client, mas 
there 
are a lot of other applications which use gears, like google docs, calendar, 
etc.

Please consider this issue as extremely high priority !!! It's unacceptable an 
important 
issued like this one without its deserved attention. More than 2 months without 
a fix 
!!!!

Snow Leopard 10.6.2
Chromium build: 4.0.257.0 (33059)
Version 4.0.4 (6531.21.10)

Original comment by marceloc...@gmail.com on 25 Nov 2009 at 5:31

[GoogleCodeExporter]

@47 Does this mean that Google will be moving towards standards-based offline 
storage and geolocation 
instead of their proprietary Gears stuff? I hope so, and I hope that this 
happens sooner rather than later, as I'd 
like to be able to use these features on your sites...

Original comment by mike...@gmail.com on 25 Nov 2009 at 6:37

[GoogleCodeExporter]

I can't imagine how this would be a 'medium' priority issue.

Original comment by simo...@gmail.com on 27 Nov 2009 at 3:01

[GoogleCodeExporter]

Please, raise the priority.

Original comment by caio.gon...@gmail.com on 30 Nov 2009 at 4:28

[GoogleCodeExporter]

Please raise the priority. We're all moving to Snow Leopard.

Original comment by branst...@gmail.com on 30 Nov 2009 at 7:22

[GoogleCodeExporter]

Attention!

The severity of an issue is measured by how many people that have starred it. 
Whenever you post a comment 
here, an e-mail is sent to all the starrers. Many people will un-starr issues 
that gets a lot of comments. This 
is especially true when all the comments are about how severe the issue is. The 
starrers already agree with 
you about the severity, because they have starred it. This makes posting 
comments about severity counter 
productive: Google won't read it, starrers will, and your comment is more 
likely to cause people to un-starr it 
than it is making Google prioritize the issue.

So please, let this be the last comment for a while. Just starr the issue, and 
hope for the best. Pointing out the 
severity in comments is pointless.

Original comment by augustlilleaas on 30 Nov 2009 at 7:39

[GoogleCodeExporter]

Thought I'd post this bit of info from this article:
http://www.techcrunch.com/2009/11/30/chrome-for-mac-features/

"Gears, which allows for offline web app functionality, is completely off the 
table
as a Chrome for Mac feature right now, according to project lead Mike Pinkerton 
(he
actually noted this back in July). Apparently, Google plans to push ahead with 
full
HTML5 support rather than rely on Gears, at least on the Mac."

So it looks like Google is switching to HTML5 rather than gears for present and
future mac development, hence the delay.

Original comment by paulwmor...@gmail.com on 30 Nov 2009 at 11:07

[GoogleCodeExporter]

@57 I believe you are misinformed as to how Project Hosting works on Google 
Code, 
please see this support page for more information on the issue life-cycle and 
priority labeling. http://code.google.com/p/support/wiki/IssueTracker#Concepts 
The 
priority of an issue is an editable label, and is not automatically assigned 
based on 
how many people have starred the issue--unless that is the manual process which 
the 
google gears folks have said they follow.

IMHO the only reason this is a Priority-Medium issue, is the fact that people 
haven't 
publicized the issue much. The reality appears to be that google could care 
less 
about their mac users, based on how much attention they appear to have given 
this 
issue. I've loved using google products for years, but to simply drop support 
for 
something in this fashion certainly makes me want to research other products in 
case 
google decides to drop support for other features/applications in project 
hosting or 
google apps.

Original comment by Immutate on 1 Dec 2009 at 2:23

[GoogleCodeExporter]

@59, I think that 58 seems to have answered the big question for us, if his 
answer is indeed correct. Basically, 
Google isn't ditching us. But they aren't going to waste time on Gears for Mac 
because they are basically 
'leapfrogging' to HTML 5 instead. As much as it stinks for us as Mac users, it 
doesn't make much sense for them 
to continue developing a technology that was only a temporary fix anyway and 
apparently is becoming obsolete. 
So, as is often unfortunately the case for Mac users, we must have some 
patience. Making our voice heard isn't 
going to get us Gears anytime soon because they aren't going to do it. But if 
this gets some attention, perhaps 
they will do what they can to speed along the HTML 5 solution.

Original comment by mkono...@gmail.com on 1 Dec 2009 at 2:51

[GoogleCodeExporter]

@59: I am not misinformed, but I can see why you thought I was. I were speaking 
in terms of conventions, 
though - most project owners uses the number of stars on an issue to determine 
what should be deemed 
important.

As @58 points out, it seems that the reason for the severity isn't that Google 
doesn't care about Mac, it's 
because Google doesn't care about gears, to put it bluntly. Here's another link 
referencing the same source on 
google going towards HTML5 instead of Gears.

http://latimesblogs.latimes.com/technology/2009/11/google-gears.html

Original comment by augustlilleaas on 1 Dec 2009 at 3:06

[GoogleCodeExporter]

Longterm wise it surely makes sense to go this way for Google as well as for 
the user, but still, the way Google 
handles this issue is not the finest way.
I hope there is something in the pipeline since the iPhone version of GMail is 
already making full use of HTML5 
and offline storage. As a bad interim solution one can set the Safari User 
Agent to Mobile Safari to test and 
maybe use this feature once in a while...
It is really weird that the full client lacks behind the iPhone version somehow.

Original comment by johannes...@gmail.com on 1 Dec 2009 at 3:20

[GoogleCodeExporter]

@60: I'm certainly glad to hear that google is moving towards the new HTML 5 
standard, and hope that the project moves 
quickly. Snow Leopard has been GA for more than 3 months now, and we've only 
just been informed what direction google is 
moving toward in regards to gears in Snow Leopard/Safari. Combine that with the 
developer preview of Snow Leopard which has 
been available since June, I would have assumed development would be further 
along, or we'd at least have been told of this 
sooner. Here's hoping we can get some traction on google apps offline 
functionality, regardless of the technology used to re-
implement the feature.

@61: That would be the manual process I wasn't sure about ;) I really wish 
google would mark this defect's status as WontFix 
and update the gears homepage to accurately represent their stance. It seems as 
though this defect and all of the other 
gears/Snow Leopard issues that have been filed are simply being ignored.

Original comment by Immutate on 1 Dec 2009 at 4:17

[GoogleCodeExporter]

Maybe exemplary: Saft extends Safari in any one of three ways, 
only one of which is limited to 32-bit. Screen shot at 
http://www.wuala.com/grahamperrin/public/2009/12/02/a/001.png

The embrace of HTML 5 is welcomed. 

Parallel to that: if any developer is inclined to progress this issue 847, use 
of SIMBL may be most appropriate. 

http://www.culater.net/software/SIMBL/SIMBL.php

Original comment by grahampe...@gmail.com on 3 Dec 2009 at 8:03

[GoogleCodeExporter]

Folks, take a hint from Issue 335, and use the issue tracker to share 
workarounds, or patches.  If your comment doesn't 
substantively help solve this issue, it doesn't belong here.  This project has 
a mailing list, and that's the proper place for your hopes, 
your fears, your burning questions, and your idle ruminations.

It might seem counter-intuitive, but adding unproductive comments actually 
makes it less likely that this issue will be fixed.  This is 
an open-source project.  Yes, the committers are Googlers, but there's nothing 
stopping you from checking out the code and trying 
to fix this issue.  In fact, someone started to do just that @40, but left @46 
because of your "self-important whining."  With the Gears 
Team seemingly focused on Windows-related issues, it's all the more important 
that issues like this one be attractive for outside 
developers to solve.

In the spirit of taking my own advice, I checked out the source and tried to 
build it.  I agree with the earlier comments @40, @41, 
@46, and @64.  Scripting Additions are the new Input Manager, and it's the way 
to go for injecting code into 64-bit processes.  
Before I even started looking at the Input Manager code, however, I tried using 
Xcode to build the project.  It didn't work, so I 
updated the Xcode project and submitted a patch in Issue 984.

Original comment by lem...@gmail.com on 4 Dec 2009 at 11:33

[GoogleCodeExporter]

It seems much more likely that the team that would fix this is more dedicated 
thr chrome osx browser, 
which, once GA, should have gears as part of it natively. 

Original comment by esl...@gmail.com on 12 Dec 2009 at 8:59

[GoogleCodeExporter]

I would love to see this work for chrome and safari! Please, please raise the 
priority!

Original comment by Giambron...@gmail.com on 21 Jan 2010 at 6:12

[GoogleCodeExporter]

gears wont run on mac 10.6 .... biggggg!!!! problem please raise priority 
thanks !! 

Original comment by Yehud...@gmail.com on 10 Feb 2010 at 11:59

[GoogleCodeExporter]

forget about gears! It is  crutch for bad browsers. Do not support it, like 
google doesn't 
support others.

Original comment by Yury.Kor...@gmail.com on 11 Feb 2010 at 12:04

[GoogleCodeExporter]

(not part of google).

The reason this is not done is because its a huge amount of work, that would be 
wasted 
anyway the second that gmail etc moves over to using HTML5 for offline support.

So, the real question is, when will gmail support offline via HTML5?

Original comment by lypa...@gmail.com on 11 Feb 2010 at 10:57

[GoogleCodeExporter]

The more creative Google gets with their gmail the more we are going to see 
Apple Mail people switch over, 
particularly with the growth of smart phones. The issue of accessing your email 
when offline is very very 
important and could be the single issue that makes or breaks Mailplane for 
these customers. I was under the 
impression that offline access to email was not only easy but one of the major 
selling points of Mailplane.

Original comment by jcav...@gmail.com on 15 Feb 2010 at 4:12

[GoogleCodeExporter]

Support on Chrome for Snow Leopard :-)

Original comment by don.zo...@gmail.com on 17 Feb 2010 at 9:59

[GoogleCodeExporter]

I just updated by browser but still do not have offline gmail support/other 
gears 
features on my Snow Leopard machine.

Original comment by benzi.sh...@gmail.com on 18 Feb 2010 at 4:52

[GoogleCodeExporter]

I was forced to upgrade to Snow Leopard because I had to buy a new MAC. Now I 
cannot 
use google docs offline. Maybe if we organize a boycott of google entirely for 
everyone 
who relies on offline access for school ro work google would take notice if 
their ad 
revenue drops.

Original comment by erica...@gmail.com on 18 Feb 2010 at 8:21

[GoogleCodeExporter]

Yea, please fix this.. I'm experiencing the same issues with Snow Leopard and 
newest Safari

Original comment by adwo...@novawhite.com on 12 Apr 2010 at 12:17

[GoogleCodeExporter]

quickly!!!!

Original comment by qingp...@gmail.com on 28 Jun 2010 at 4:10

[GoogleCodeExporter]

Atlassian Confluence relies on Gears.

Original comment by ohmant...@gmail.com on 15 Sep 2010 at 7:19

[GoogleCodeExporter]

Seems strange this isn't resolved yet.  It's become core functionality for me 
and many others.  Bad user experience.

Original comment by guy.gree...@gmail.com on 6 May 2011 at 2:25