On 04/18/2010 09:44 PM, M. Edward (Ed) Borasky wrote:
Well, it seems we have enough does work and doesn't work cases to
justify me taking some Wireshark traces and trying to debug my usage,
especially if Firefox 3.6.3 is still working on wireless in Windows and
failing in wireless on openSUSE
Location has never worked for me in Win7 x64+Chrome (dev channel).
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera
On Sun, Apr 18, 2010 at 9:57 PM, Abraham Williams
i use safari + gears on OS X and it works for me. i think its only very
recent that chromium under OS X supports it.
On Sun, Apr 18, 2010 at 6:57 PM, Abraham Williams 4bra...@gmail.com wrote:
Location used to work on the Windows beta of Chrome but stopped a week or
two ago for me. It has
Chrome for OSX and Linux doesn't support Gears and never will so until
Twitter supports the HTML5 Geo spec...
2010/4/18 Raffi Krikorian ra...@twitter.com
i use safari + gears on OS X and it works for me. i think its only very
recent that chromium under OS X supports it.
On Sun, Apr 18,
Well, it seems we have enough does work and doesn't work cases to
justify me taking some Wireshark traces and trying to debug my usage,
especially if Firefox 3.6.3 is still working on wireless in Windows and
failing in wireless on openSUSE 11.2. What should I be looking for in
the traces?
On
I seem to recall hearing Gears doesn't work on Fx 3.6. I don't remember if
it was only OSX/Linux or all platforms.
Abraham
On Sun, Apr 18, 2010 at 21:44, M. Edward (Ed) Borasky zn...@comcast.netwrote:
Well, it seems we have enough does work and doesn't work cases to
justify me taking some
On my Linux (openSUSE 11.2 with some of the advanced repositories) the
message Unable to locate you. Try again is showing up, and my tweets
aren't getting geotagged. Firefox 3.6.3, Google Chrome 5.0.375.9 dev and
Seamonkey 2.0.4 all do this, and it happens for both wired and wireless
connections.
