-
Notifications
You must be signed in to change notification settings - Fork 11.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox: ReferenceError: document is not defined #141
Comments
My reply: Interesting. That code is only supposed to be hit (iirc) when the rendering is being done from the options page — not under normal email circumstances. What version of Firefox are you using? And what sites (email clients) is it failing for (besides GGroups, I guess)? I can’t seem to reproduce the problem, so… I added some additional exception logging, and made a change that might fix the problem. See changes here: 1ff7315. At the very least, we’ll be able to see exactly what exception is being thrown (maybe it’s a JSON exception or something). That change will be in the next release — this weekend at the latest. (Of course, Mozilla approval takes a while after that.) I’ll reply to this message after I release, and then please let me/us know if it’s still busted after you get the update. Thanks. Adam |
I'm using FF 25.0 on both Windows and Ubuntu. It happens on both platforms.
GMail, Outlook Web Access, Evernote.
Huh. I wonder if it's some strange brew of my add-ons and other configuration. FWIW, I'll dump by
Awesome. Thanks. I'll report back when I get the update. about:support
|
I got this error as well now. Here's the console output:
I haven't had time to look into it further. |
I can confirm the issue still occurs for me. It looks exactly as reported by @adam-p at above comment. |
Bump. Any progress to report on this issue? |
Maybe? I'm glad you reminded me... I asked on the Mozilla dev forum and I was told to test with a clean profile. So I created a pristine profile, ran Firefox (Aurora) for a whole week with Gmail open, and... no error. (I'm worried that the fact that I wasn't actively using that browser/Gmail during the week may have tainted the test, but let's ignore that for now.) So the problem is actually one of the other extensions I have installed...? And you? And @darickard? Here are the other extensions I have:
What extensions do you guys have? I guess the next thing I should do is add all of my extensions to my pristine profile and reproduce the problem. Edited to add: I just realized @stoicflame included his extensions above. We have Adblock Plus in common (and some of the dev extensions that I keep disabled until I need them). |
Here's my list:
The only add-on I see that we have in common is Adblock Plus. Although it would be sad for me to have to choose between MDH and Adblock... |
Thanks for continuing to look into this. Here are mine - all are enabled: |
I added Adblock Plus (2.5.1) to my pristine profile, opened Gmail, and left Firefox (27.0.1) open for 3 days. No result. Rendering still works fine. And now I need to shut my computer down. Maybe three days isn't long enough? Maybe letting the browser sit idle isn't a good test? When I'm able to try this again I'll make that browser instance my primary-use profile (which is going to drive me insane -- I won't have any of my other usual extensions...). |
Thanks again for staying on this and sorry about the drive to insanity. I know exactly what you mean about not having your usual extensions. The things that make Firefox great - the extensibility, customizability, etc. - make it difficult to troubleshoot. |
We will conquer this demon! ...Just not while I'm away for a week at a conference. |
Another data point: I just this behaviour in a Gmail tab that I had just opened. The browser has been open for two days (on a laptop -- lid closed on and off), but I hadn't opened Gmail in it until just now. This isn't a revelation, but I hadn't seen it before. This issue is quickly becoming a critical pain in my ass. |
I'm seeing the same behavior, and have been seeing it for a few months at least. It seems to happen when my browser's been open for awhile but I haven't tested it thoroughly enough to know if (a) that's what's actually causing trouble, and (b) how long "awhile" is. The error in the browser console:
If it's helpful, my addons are:
|
Thanks to @iagobozza in #189 I finally have a solid reproduction scenario:
It's just that easy. When you open and close a new window, it gets broken. When you open another new window, it starts working again (even in the first window). My gut feeling is that this is related to the |
Fixed in rev ad6bcc3. Phew! This will be in the next release (which will be this weekend at the latest). The problem, in brief: There are two (ish) ways of loading code modules in Firefox/Gecko: I hacked around that by storing a reference to background chrome window. It got set every time a new window opened. But... if the last window that got opened then got closed... the reference to it was invalid and our bug happened. I "fixed" it by going back to using Dirty hacks cause bugs, you guys! |
Thank you for sticking with this one, Adam. Keep up the good work! |
w00t! |
Thanks for fixing this, awesome! |
Great work! Thank you! |
woo! :D |
Reported here: https://groups.google.com/forum/#!topic/markdown-here/ikXFqkP77Ws
MDH has been working great for me until somewhat recently (a week or two?). I've noticed that there are occasions when I can't toggle the text of my reply.
I'm on Firefox, used on both Windows and Ubuntu. I open up the Browser Console and watch when I make a failed attempt to toggle. The error I get is:
That code does seem to line up with line 336 of HEAD, implying that I'm on the latest version.
Any ideas for a fix?
The text was updated successfully, but these errors were encountered: