Closed
Bug 606830
Opened 14 years ago
Closed 3 years ago
GMail compose button and settings link don't work when dom.storage.enabled is false
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: lior6996, Unassigned)
References
()
Details
(Whiteboard: [platform-rel-Google] [platform-rel-Gmail])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; he; rv:1.9.2.11) Gecko/20101012 Firefox/3.6.11 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; he; rv:1.9.2.11) Gecko/20101012 Firefox/3.6.11 (.NET CLR 3.5.30729)
compose mail button don't work, also the reply button - it just gives a messeage "loading" and nothing happens.
Reproducible: Always
Steps to Reproduce:
1.try to compose mail or reply with ver 3.6.11
2.
3.
Actual Results:
loading message
nothing else
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12pre) Gecko/20101026 Namoroka/3.6.12pre
Works for me in original build and also the latest nightly build. When clicking the compose button while the page is loading, It displays loading for few seconds and then it opens the compose window. Reply also works for me.
Please try if it works fine in safe mode try by creating a new profile.
https://support.mozilla.com/en-US/kb/Safe+Mode
https://support.mozilla.com/en-US/kb/Managing+profiles#Creating_a_profile.
Reporter | ||
Comment 2•14 years ago
|
||
thanks.
found the real problem the cause gmail button not to work (for future reference):
the dom.storage.enabled option was set on false, probably because of betterprivacy addon (not sure about that) - when changing this setting to enabled it works perfect.
Comment 3•14 years ago
|
||
"Policy Manager" (addon 7066) has code to manage this pref, but I don't think it changes it unless the user selects the option.
It looks like an earlier version of BetterPrivacy (addon 6623) had an option to disable DOM storage. The current version instead clears DOM storage on exit (as an option) and attempts to convert the old setting and reenable DOMStorage. It's possible you have the older version, or that in between there was a version that switched to the new behavior and didn't convert correctly.
"Prefswitch" (addon 6485) can change the setting
This is not a complete list, just some that popped out early in a search.
I believe this bug (from an extention, in my case not BetterPrivacy), also affects Firefox 4.0b6.
dom.storage.enabled was set to false on my installation. Reverting it to true let me compose emails again using Gmail.
I am using FF 4.0b6 and this bug happened recently. So its definitely a new or updated version of an extension I installed recently.
Comment 5•14 years ago
|
||
(In reply to comment #4)
> I am using FF 4.0b6 and this bug happened recently. So its definitely a new or
> updated version of an extension I installed recently.
...or a recent change in GMail.
Nightly builds of Minefield (and the upcoming beta 7) have different behavior with regards to the localSession object due to the fix for bug 599479. In Minefield you can do code like
if (!window.localStorage)
// you have an old browser (or storage disabled)
else
// storage will work
Up to Firefox 4.0b6 the localStorage object always exists even if storage is disabled, but attempts to use it when disabled will throw. If Gmail code was changed to do simple object detection exceptions could very well cause these symptoms.
Updated•14 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: compose button don't work → GMail compose button and settings link don't work when dom.storage.enabled is false
If this bug is caused by Gmail not catching exceptions when checking for storage (which "works" on trunk thanks to the fix for bug 599479 and fails everywhere else), then once bug 599479 has landed on the branches (currently approved for 1.9.2.13 and 1.9.1.16), this bug should be fixed.
Updated•9 years ago
|
Whiteboard: [platform-rel-Google] [platform-rel-Gmail]
Updated•9 years ago
|
platform-rel: --- → ?
Updated•8 years ago
|
platform-rel: ? → ---
Hi,
I'm marking this ticket as Resolved - WFM as I understand this is an outdated request.
Please reopen it in case this is still active.
Thanks,
Virginia
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•