The lack of a JavaScript switch in Firefox (Android) - why?
I have noted from a web search that the subject of Javascript in Firefox (Android) has caused issues for some users of this browser.
I understand that JavaScript is now enabled by default in the standard version of Firefox (Android). It appears that once upon a time there was a config setting that could be tweaked to switch JavaScript on or off, but that setting may no longer work. Additionally, I also understand there are add-ons for the Android version of Firefox that can, amongst other things, apparently switch JavaScript on or off.
People here might be surprised to learn that the minimalist Firefox Focus (Android) browser already has a built-in, easily accessible, switch to turn JavaScript on or off:
Settings > Privacy & Security > Web Content > Block JavaScript
So, the point I would like to raise with Mozilla (but it seems to be impossible to contact them directly) is, if it is available in Firefox Focus (Android), why the heck is this switch not available in the mainstream, standard version of Firefox (Android)? It makes absolutely no sense not to have it, surely?
I would suggest that a good place to include a JavaScript switch would be in the 'Site permissions' section of Firefox (Android) settings. It is merely a suggestion as, for example, within the rather useful competitor Vivaldi (Android) browser there is such a switch located here:
Settings > WEB PAGES > Site settings > JavaScript
As for why there should be a JavaScript switch within Firefox (Android), that question is largely irrelevant. Mozilla have already seen a need to include it in Firefox Focus (Android), so what possible good reason could there be for not including it in Firefox (Android)? It mystifies me, and it's omission is an inconvenience too.
Does anyone here have a sensible answer to this question?
Modified by SaturnV
Chosen solution
Hi,
The people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers. If you want to leave feedback for developers, you can go to this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.
You can also file a bug report or feature request. See File a bug report or feature request for Mozilla products for details.
Read this answer in context 👍 1All Replies (6)
We don't have any answer about that. Please check it in issue #11469.
TyDraniu, thanks for your prompt response, and the link.
My main point with all this is that if a Javascript switch is available in one Mozilla Android browser, there is unlikely to be a sensible reason why it is not available in another Mozilla Android browser! The coding to include it cannot be difficult, and it already exists, and functions well, in Firefox Focus!!
It's a crazy situation!!
Hi
Have you tried the NoScript add-on for Firefox for Android?
Paul, thanks for your suggestion, but as my opening question indicates, I am already aware of 'solutions' like NoScript. But the existence of such an add-on does not excuse the daft situation where Firefox Focus (Android) has the useful JavaScript switch, but Firefox (Android) does not!
I am trying to get to the reason why the switch is absent in Firefox (Android), not alternative means of achieving JavaScript switching. I, personally, cannot see any sensible reason for the omission of a Javascript switch in Mozilla's mainstream Android browser!
Chosen Solution
Hi,
The people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers. If you want to leave feedback for developers, you can go to this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.
You can also file a bug report or feature request. See File a bug report or feature request for Mozilla products for details.
Paul, thanks again, and I appreciate the weblinks - I will head on over to them and repeat my query in an appropriate spot.
It is the knowledgeable volunteers, such as yourself, who know where to go to 'get Mozilla's attention', so in many respects my query here has achieved a result.