1195557 - Error when Opening Google Docs

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Alex Davis [:adavis]]

Attachment: Screen Shot 2015-08-17 at 12.05.33 PM.png

A couple of us are unable to open Google Docs with the Dev Edition of Firefox. I just updated to 42.0a2 (2015-08-17) and it didn't resolve the problem.

I've attached a screenshot of the error message we're seeing.

I was running moments ago the beta of FX40 too and it worked no problem there. I updated it to Beta 41.0b1 and it started to display the same error message.

Here is the error message:
"This error has been reported to Google and we'll look into it as soon as possible. Please reload this page to continue."

Reloading the page does not resolve the problem.

Comment 1

[Bogdan Maris, Desktop QA]

I was able to reproduce this using latest Aurora, latest Nightly and Firefox 41 beta 2 but NOT with Firefox 40.0 RC.

This issue started when Nightly changed from 40.0a1 to 41.0a1

Regression range:

Last good buildID: 20150511030203
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2015/05/2015-05-11-03-02-03-mozilla-central/
https://hg.mozilla.org/mozilla-central/rev/d8420a541d1c

First bad buildID: 20150511122605
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2015/05/2015-05-11-12-26-05-mozilla-central/
https://hg.mozilla.org/mozilla-central/rev/502e1a5e722f

Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d8420a541d1c&tochange=502e1a5e722f

Console output:
> Use of getAttributeNode() is deprecated. Use getAttribute() instead. 3598078500-kix_main_i18n_kix_core.js line 160 > eval:285:0
> unsafe CPOW usage contentPolicy.js:644:0
> unsafe CPOW usage contentPolicy.js:645:0
> unsafe CPOW usage contentPolicy.js:663:0

Comment 2

[situmam]

(In reply to Bogdan Maris, QA [:bogdan_maris] from comment #1)
> I was able to reproduce this using latest Aurora, latest Nightly and Firefox
> 41 beta 2 but NOT with Firefox 40.0 RC.

I can confirm the same results on both Ubuntu 14.04 and Mac OS X. This is definitely OS independent.

Comment 3

[Scott Frost]

I had this issue too, starting this morning.  Several others on reddit did as well when I asked about it - http://redd.it/3hfs8c

Disabling HTTP Everywhere, uBlock, etc don't seem to help.  It may be something that Google changed on their end, because it seems to work in Chromium and Edge.

Comment 4

[Bill Walker [:bwalker] [@wfwalker]]

+1 this is seriously cramping my style using the Moz corporate google account. Replicated in 42.0a2 on Mac OS X 10.10.4

Comment 5

[Bill Walker [:bwalker] [@wfwalker]]

Web Console shows, upon page reload:

CustomError: Error in protected function: Operation is not supported <unknown>
NotSupportedError: Operation is not supported 3598078500-kix_main_i18n_kix_core.js:1677:0
GET 
https://docs.google.com/document/d/15DljFEUB7jqaAXSRgl7jtRorRyxhalqHmGM5VmqpctQ/edit [HTTP/2.0 200 OK 276ms]
TypeError: this.j is undefined

Comment 6

[Bill Walker [:bwalker] [@wfwalker]]

note that the kix_main_i18n_kix_core.js error message was also seen in bug reports like bug 807743

Comment 7

[Alice0775 White]

(In reply to Bill Walker [:bwalker] [@wfwalker] from comment #5)
> Web Console shows, upon page reload:
> 
> CustomError: Error in protected function: Operation is not supported
> <unknown>
> NotSupportedError: Operation is not supported
> 3598078500-kix_main_i18n_kix_core.js:1677:0
> GET 
> https://docs.google.com/document/d/
> 15DljFEUB7jqaAXSRgl7jtRorRyxhalqHmGM5VmqpctQ/edit [HTTP/2.0 200 OK 276ms]
> TypeError: this.j is undefined

This seems to be Bug 1195795

Comment 8

[situmam]

Using FF 41.b2, I was able to successfully create a new google document, edit it and save it. I then closed the tab and re-opened the file I just edited and it worked. I was successful in opening the file, editing it and saving it again.

Comment 9

[Lisa Brewster [:adora]]

I've been having this issue off and on for weeks, usually getting at least one error per day (across around a dozen open Docs tabs that stay open for days/weeks).  It started triggering 100% late last night (maybe midnight pacific) and persisting until morning.  Sometime midday I think I stopped seeing it.  

Also worth noting that I currently have all extensions disabled to troubleshoot a separate issue.  42.0a2

Comment 10

[situmam]

(In reply to situmam from comment #2)
> (In reply to Bogdan Maris, QA [:bogdan_maris] from comment #1)
> > I was able to reproduce this using latest Aurora, latest Nightly and Firefox
> > 41 beta 2 but NOT with Firefox 40.0 RC.
> 
> I can confirm the same results on both Ubuntu 14.04 and Mac OS X. This is
> definitely OS independent.

Today, the problem is gone. I can open google docs without any issues. I suspect this was all on google's side.

Comment 11

[Scott Frost]

I agree with [e-mail].  Google appears to have hotfixed it on their end.  I haven't updated my firefox builds or changed extensions and now it's working fine.

Recommend closing this bug.

Comment 12

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Bogdan, I noticed that you were able to repro this bug. Given comment 11, would you be able to retry this scenario on your end? This will help us decide whether anything needs to still be done on our end. Thanks!

Comment 13

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Tracked for now. Will untrack if Bogdan tells us this works well.

Comment 14

[Bogdan Maris, Desktop QA]

(In reply to Ritu Kothari (:ritu) from comment #12)
> Bogdan, I noticed that you were able to repro this bug. Given comment 11,
> would you be able to retry this scenario on your end? This will help us
> decide whether anything needs to still be done on our end. Thanks!

Yes, I can also confirm that this issues does NOT reproduce anymore across platforms (Windows 7 64-bit, Ubuntu 14.04 32-bit and Mac OS X 10.10.4) using Firefox 41beta2, latest Aurora 42.0a2 and latest Nightly 43.0a1. Closing as worksforme!

Comment 15

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Untracked for FF41 as this was an issue on Google's side which has been fixed and google docs work A-OK with 41, 42 and 43.