On the last page you click on the blue [Post Question] and not on the green [Automatically Add] button. Or are you referring to the green [Ask this] button.
On the last page you click on the blue [Post Question] and not on the green [Automatically Add] button. Or are you referring to the green [Ask this] button.
The "Ask this" button does nothing. I cannot even get the title submitted. I was able to submit the question finally, with Safari. Are you trying to lock out Mozilla browser users?
The "Ask this" button does nothing. I cannot even get the title submitted. I was able to submit the question finally, with Safari. Are you trying to lock out Mozilla browser users?
maybe post screenshots and/or detailed description of what you are actually doing
hi finitarry, it works fine for me on mac os x 10.9.5, no add-ons, firefox nightly 36
# https://support.mozilla.org/en-US/questions/new
# clicked on Firefox for Android
# clicked on Download install and migration"
# filled in title clicked "Ask this"
# "None of these solve my problem"
# "Post Question"
https://support.mozilla.org/en-US/questions/1027183
maybe post screenshots and/or detailed description of what you are actually doing
You posted another thread here recently about buttons that don't work. Maybe something in that thread is helpful?
*[/forums/contributors/710645] Buttons not working on the support site
I followed the same procedure with Safari that I used with SeaMonkey and Firefox. It worked with Safari.
1. Click "Ask a question" at top of a page (while being logged in).
2. Choose Firefox for Desktop.
3. Choose a category.
4. Try an article and find that it is no help.
5. Type title of question.
6. Click "Ask this".
I followed the same procedure with Safari that I used with SeaMonkey and Firefox. It worked with Safari.
1. Click "Ask a question" at top of a page (while being logged in).
2. Choose Firefox for Desktop.
3. Choose a category.
4. Try an article and find that it is no help.
5. Type title of question.
6. Click "Ask this".
Alice,
Avoiding filtering geo.mozilla.org/country.js did not help this time. I thought that was supposed to be fixed anyway? I was able to post new questions before. Why not now? Safari has a subscription to EasyPrivacy, as do Firefox and SeaMonkey. If that filter were the problem, would I not also have a problem using Safari?
Alice,
Avoiding filtering geo.mozilla.org/country.js did not help this time. I thought that was supposed to be fixed anyway? I was able to post new questions before. Why not now? Safari has a subscription to EasyPrivacy, as do Firefox and SeaMonkey. If that filter were the problem, would I not also have a problem using Safari?
I followed your six step process and it worked again (had to add a step 7 and 8: 7. "None of these solve my problem" 8. "Post Question" , so what's the problem Finitarry :-) ?
Is it:
geo-ip
an add-on perhaps?
something else?
hi Finitarry
I followed your six step process and it worked again (had to add a step 7 and 8: 7. "None of these solve my problem" 8. "Post Question" , so what's the problem Finitarry :-) ?
Is it:
# geo-ip
# an add-on perhaps?
# something else?
Alice,
Avoiding filtering geo.mozilla.org/country.js did not help this time. I thought that was supposed to be fixed anyway? I was able to post new questions before. Why not now? Safari has a subscription to EasyPrivacy, as do Firefox and SeaMonkey. If that filter were the problem, would I not also have a problem using Safari?
If no one has another suggestion:
Why don't you try disabling AdBlock Plus on support.mozilla.org in Firefox and SeaMonkey? If that works then it's an Adblock Plus issue.
''finitarry [[#post-62529|said]]''
<blockquote>
Alice,
Avoiding filtering geo.mozilla.org/country.js did not help this time. I thought that was supposed to be fixed anyway? I was able to post new questions before. Why not now? Safari has a subscription to EasyPrivacy, as do Firefox and SeaMonkey. If that filter were the problem, would I not also have a problem using Safari?
</blockquote>
If no one has another suggestion:
Why don't you try disabling AdBlock Plus on support.mozilla''.''org in Firefox and SeaMonkey? If that works then it's an Adblock Plus issue.
Did you disable dom storage? That might be the problem.
Enable it by setting dom.storage.enabled to true in about:config. A lot of things on the site need dom storage to be enabled.
Did you disable dom storage? That might be the problem.
Enable it by setting dom.storage.enabled to true in about:config. A lot of things on the site need dom storage to be enabled.
A lot of things on the site need dom storage to be enabled.
Related SUMO bug filed 2014-05-29 by Gingerbread Man
Bug 1017850 - Display a warning when DOM storage is disabled (dom.storage.enabled = false)
''Noah_SUMO [[#post-62533|said]]''
<blockquote> A lot of things on the site need dom storage to be enabled.
</blockquote>
Related SUMO bug filed 2014-05-29 by Gingerbread Man
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1017850 Bug 1017850] - Display a warning when DOM storage is disabled (dom.storage.enabled = false)
I tried disabling Adblock Plus on the support forum. That did not help. I really do not want to enable DOM storage. It has the capability of a supercookie, and I really dislike the idea of all kinds of information being stored in there without my being able to see or control it. Why would there suddenly be a need for that now anyway? It was not needed before.
I tried disabling Adblock Plus on the support forum. That did not help. I really do not want to enable DOM storage. It has the capability of a supercookie, and I really dislike the idea of all kinds of information being stored in there without my being able to see or control it. Why would there suddenly be a need for that now anyway? It was not needed before.
Roland,
The problem is that "Ask this" does nothing. It is not an add-on causing the problem. I tried disabling all the extensions, and it did not help.
Roland,
The problem is that "Ask this" does nothing. It is not an add-on causing the problem. I tried disabling all the extensions, and it did not help.
I really do not want to enable DOM storage. It has the capability of a supercookie, and I really dislike the idea of all kinds of information being stored in there without my being able to see or control it. Why would there suddenly be a need for that now anyway? It was not needed before.
When you reset dom.storage.enabled to the default "true" value in about:config does the problem go away?
P.S. I just tested and I also can't post a new question when dom.storage.enabled is set to false. Resetting the preference to "true" fixes it.
''finitarry [[#post-62542|said]]''
<blockquote>
I really do not want to enable DOM storage. It has the capability of a supercookie, and I really dislike the idea of all kinds of information being stored in there without my being able to see or control it. Why would there suddenly be a need for that now anyway? It was not needed before.
</blockquote>
When you reset '''dom.storage.enabled''' to the default "true" value in about:config does the problem go away?
P.S. I just tested and I also can't post a new question when '''dom.storage.enabled''' is set to '''false'''. Resetting the preference to "true" fixes it.
Yes, enabling DOM storage fixes the problem, but I do not like that. Why suddenly is there a need for that? There is no need for DOM storage enabling to answer questions on the support forum, so why should it be needed to post new questions? I would rather use Safari to post questions than leave that enabled. There is obviously no need for that on this forum.
Yes, enabling DOM storage fixes the problem, but I do not like that. Why suddenly is there a need for that? There is no need for DOM storage enabling to answer questions on the support forum, so why should it be needed to post new questions? I would rather use Safari to post questions than leave that enabled. There is obviously no need for that on this forum.
Hopefully whoever is reviewing SUMO bugs will reply.
''finitarry [[#post-62545|said]]''
<blockquote>
Yes, enabling DOM storage fixes the problem, but I do not like that. Why suddenly is there a need for that?
</blockquote>
I added a link to this thread in the related bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1017850#c1
Hopefully whoever is reviewing SUMO bugs will reply.
Hopefully whoever is reviewing SUMO bugs will reply.
TIL: DOM storage is a thing and for some strange (:-) ?!?) reason we need it on SUMO to ask a question :-) Thanks Alice and Finitarry!
I'll leave it to Ricky Rosario and SUMO-DEV wizards to answer why we need DOM storage!
Cheers!
...Roland
''AliceWyman [[#post-62546|said]]''
<blockquote>
''finitarry [[#post-62545|said]]''
<blockquote>
Yes, enabling DOM storage fixes the problem, but I do not like that. Why suddenly is there a need for that?
</blockquote>
I added a link to this thread in the related bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1017850#c1
Hopefully whoever is reviewing SUMO bugs will reply.
</blockquote>
Note that this forum also uses DOM storage to store the status of some folded items (collapsed or not).
So when localStorage is disabled you won't keep such the folded status.
I currently see these: ((x) denotes the content size of a key)
localStorage[4]: [1]:question-tools.folded (4):true [2]:tags-list.folded (4):true [3]:question-details.folded (4):true [4]:editing-tools-sidebar.folded (4):true
Note that this forum also uses DOM storage to store the status of some folded items (collapsed or not).
So when localStorage is disabled you won't keep such the folded status.
I currently see these: ((x) denotes the content size of a key)
localStorage[4]:<br>[1]:question-tools.folded (4):true<br>[2]:tags-list.folded (4):true<br>[3]:question-details.folded (4):true<br>[4]:editing-tools-sidebar.folded (4):true
Bug 1017850 - Don't break the site (js) if localStorage isn't available
This bug was fixed yesterday:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=1017850 Bug 1017850] - Don't break the site (js) if localStorage isn't available
