651619 - SeaMonkey browser does not work with Google sites and Docs

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[tandbmarks]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.18) Gecko/20110320 SeaMonkey/2.0.13
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.18) Gecko/20110320 SeaMonkey/2.0.13

SeaMonkey does not work with Google Docs and sites. Will not add new files to sites. Will not upload files to Google Docs.

Reproducible: Always




This is not a bug, but a calendar sure would be nice in the SeaMonkey Suite.

Thank you.

Other that the above bugs and the suggestion, SeaMonkey is great.

Comment 1

[Robert Kaiser]

(In reply to comment #0)
> SeaMonkey does not work with Google Docs and sites. Will not add new files to
> sites. Will not upload files to Google Docs.

Could you try with the new 2.1 Beta 3 version? This might actually be an error on the Google side of things, and 2.1 masks itself as Firefox, which makes a lot of such errors on websites go away.

Comment 2

[u331436]

Using SM 2.2a1pre (nightlies), I see that Google docs are not editable (i.e. Excel clone, can't update a cell) with SM, it works fine with FF 4.0.

I tried to test again without "NoScript", same result.

Comment 3

[Robert Kaiser]

Don't compare apples and oranges, please. Compare SeaMonkey _2.1b3_ with Firefox 4.0 and SeaMonkey 2.2a1pre with Firefox Nightly (6.0a1), as those are the versions that match. We know that Google has done some strange "browser sniffing" at times and that they actually had or have a problem with Firefox Nightly, for example.

Comment 4

[u331436]

Well, using FF6.0 nightly works with Google docs (Excel-like document that I use every day. I can update it with FF6.0 nightly and I can only open/read it with SM2.2a1pre...
Surely Google has some strange sniffing ways... :)

Comment 5

[Philip Chee]

As a test, set general.useragent.override to the Firefox UA string.

Comment 6

[u331436]

I test the general.useragent.override set to the FF UA string, but no joy.
I did a bit more testing to see that mostly Google Docs work, only the spreadsheet is not working. for some reason, I get with SM2.2a1pre the spreadsheet but no read/write access to it, when I can edit OK the same spreadsheet with FF 6.01.... Strange and inconclusive.

Comment 7

[Tony Mechelynck [:tonymec]]

(In reply to comment #6)
> I test the general.useragent.override set to the FF UA string, but no joy.
> I did a bit more testing to see that mostly Google Docs work, only the
> spreadsheet is not working. for some reason, I get with SM2.2a1pre the
> spreadsheet but no read/write access to it, when I can edit OK the same
> spreadsheet with FF 6.01.... Strange and inconclusive.

Just a wild guess: maybe this spreadsheed is only editable by a certain set of Google accounts, and your Fx6 profile has the Password Manager data for such a user but your SeaMonkey profile doesn't? What happens if you load that page in Fx6 on a new profile?

Comment 8

[u331436]

Thanks for the help Antoine, but I log in Google from SM and FF with the same credentials. I can't figure out what goes wrong here...
I tried to create a new spreadsheet from two different accounts on Google and I get the same result: no access to the edit buttons (file save, save as, etc...)and spreadsheet edition (cell content, cell color...).
I'll try with a test profile on SM then.

Comment 9

[u331436]

Mmm, my test profile works fine ! I guess it is not easy to compare profile, so I might have to transfer all my various accounts into a new (fresh) profile, my passwords and so on... :) .
Bottom line: SM2.2 works OK with google docs (with a clean profile).

Comment 10

[Tony Mechelynck [:tonymec]]

In reply to comment #9:
To compare your profiles (in the sense of: hunting for why one of them works and the other doesn't), browse to about:support with each of them, save each result to the clipboard (using the button near the top) then from there to a file, and take a diff of these files. Pay special attention to the list of extensions (you may disregard entries with enabled=false but watch out for sequence permutations between versions) and the list of modified preferences (which are listed in alphabetical order to analyzing that part of the diff should be something straightforward).

Comment 11

[Philip Chee]

A quicker procedure.
Restart in safe mode:
Does this fix the problem? If so it's probably an extension problem or a preference that is set to a non-default value.
If it is a problem caused by an extension (e.g. NoScript or various video downloaders) Go to the Addons Manager and disable all extensions, then restart in normal mode. If this fixes the problem, re-enable your extensions one by one until the problem comes back.

Comment 12

[u331436]

Hi Tony and Philip,
I tried both approaches and did not succeed !
Comparing profiles via about:support and diff did not bring any result.
Tried to disable all extensions and also tried safe mode without any result.
However, my "simple" test profile works fine !
I then added Noscript, adblock on the test profile for the same (good result).
I searched the Google help which is mainly dealing with FF UA for older version of SM (SM2.0 or so).
Still confused.
Note that the "about:support" diff shows a lot of printer-related prefs, which i assumed were not related to the issue.

Comment 13

[u331436]

Hi Tony and Philip,
I tried both approaches and did not succeed !
Comparing profiles via about:support and diff did not bring any result.
Tried to disable all extensions and also tried safe mode without any result.
However, my "simple" test profile works fine !
I then added Noscript, adblock on the test profile for the same (good result).
I searched the Google help which is mainly dealing with FF UA for older version of SM (SM2.0 or so).
Still confused.
Note that the "about:support" diff shows a lot of printer-related prefs, which i assumed were not related to the issue.

Comment 14

[Tony Mechelynck [:tonymec]]

Dominique, I'm resolving this bug INVALID on the assumption that it isn't a Mozilla bug (but that some customization of yours caused the Google site to react strangely).

I hope that you can find out what was the problem, or at least build up a profile where it doesn't happen.

Comment 15

[u331436]

Resolving as invalid is fine with me.
I should change my main machine soon and I will then rebuild a complete new profile from scratch. It should be fine then, much cleaner than my current profile which has some origin in the old Netscape days.... ;-)
Thanks for the support, and kudos for the work on Seamonkey development !!