X
Tap here to go to the mobile version of the site.

Support Forum

How do I make all windows/pop-ups open in the background?

Posted

Okay, there are a few questions I'd like to ask of this great, great community that Mozilla has created. 1. How do I make all windows/pop-ups open in the background opposed to the foreground? 2. How do I stop the pop-up window from becoming active (i.e putting itself in front of all other windows to get my attention)? I heard this is referred to window "Raise or lower" or something like that. I've read a few articles but haven't cracked the code (not literally) so, any help is hugely appreciated, thank you in advance everyone! 3. Could there be a way where you can make it open in tab form instead but in another window (a specific window for all of the pop-ups to go into? 4. Could there be an add-on to help?

Note: I can't get rid of the popups as it helps my cause.

          Putting the popups in another tab decreases my productivity massively.
          This looks interesting: https://support.mozilla.org/en-US/questions/995152

I know this is random but the Firefox community consists of some great, smart individuals around here so, take it from here everyone!

Okay, there are a few questions I'd like to ask of this great, great community that Mozilla has created. 1. How do I make all windows/pop-ups open in the background opposed to the foreground? 2. How do I stop the pop-up window from becoming active (i.e putting itself in front of all other windows to get my attention)? I heard this is referred to window "Raise or lower" or something like that. I've read a few articles but haven't cracked the code (not literally) so, any help is hugely appreciated, thank you in advance everyone! 3. Could there be a way where you can make it open in tab form instead but in another window (a specific window for all of the pop-ups to go into? 4. Could there be an add-on to help? Note: I can't get rid of the popups as it helps my cause. Putting the popups in another tab decreases my productivity massively. This looks interesting: https://support.mozilla.org/en-US/questions/995152 I know this is random but the Firefox community consists of some great, smart individuals around here so, take it from here everyone!

Chosen solution

I pulled these prefs from a long defunct JavaScript extension when that extension was no longer compatible when a new version of Firefox came out. Probably goes back to before Firefox 3.0 or 3.5 - I just don't recall.

// advanced JavaScript Options:
user_pref("dom.disable_window_move_resize", true);
user_pref("dom.disable_window_open_feature.directories", true);
user_pref("dom.disable_window_open_feature.menubar", true);
user_pref("dom.disable_window_open_feature.personalbar", true);
user_pref("dom.disable_window_open_feature.scrollbars", true);
user_pref("dom.disable_window_open_feature.toolbar", true);

I have been carrying them forward via a user.js file for many years now, and that is the format used for prefs added in the user.js file. http://kb.mozillazine.org/User.js_file I use the user.js file to help me keep track of all the prefs that I commonly change in about:config for every new Profile that I create. One file to "drop" into a new Profile, rather then spends many minutes remembering and setting them all via about:config. I also do that with userChrome.css and userContent.csss files - the triumvirate of Firefox "user" files.

Type about:config in the URL bar and hit Enter. Paste this in the Search field at the top dom.disable_window_ and see all those hidden prefs (and a few more) as still being available in Firefox 57.

Sorry, I can't answer your 5 questions as there are too many variables involved with "new" and "open" actions for windows; and some are done via JavaScript which can affect how Firefox handles them. And as far as opening those in Tabs, the JavaScript links can "throw a wrench in the works" as to whether the user has control over if or how Firefox prefs can affect actions.

A far as an extension goes, I have no idea - but my guess is that it is doubtful, but don't let me dissuade you from looking for such an extension. Sorry that I can't help you more with specific answers for your 5 questions, but my "desire" for re-learning after changes to Firefox died back in the Firefox 3# versions, as API's were changed and the old API's became deprecated thru the 30's, 40's, and into the 50's versions. Still using ESR 38.0.5 and 47.0.1 where "signing" for extensions isn't mandatory. IMO, less "evil" and far safer with NoScript by using the older versions of Firefox, and better than switching to a different browser that wouldn't be as configurable and might have a steep learning curve. Stick with the "known evil" and avoid a new one that has a steep curve attached.

I am playing with Quantum a bit every day to learn what it is capable of and to learn what was "killed" as far as user configuration possibilities or options are concerned. But my goal for using Quantum as my primary browsers extends well into next year - maybe the Firefox 60 or 61 versions.

Read this answer in context 2
Quote

Additional System Details

Installed Plug-ins

  • Shockwave Flash 28.0 r0

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

More Information

Helpful Reply

This could also help answer my first question but it's outdated and the directory is no longer there... Tools > Options > Content : JavaScript > Advanced > Allow Scripts to: [X] "Raise or lower windows"

This could also help answer my first question but it's outdated and the directory is no longer there... '''Tools > Options > Content : JavaScript > Advanced > Allow Scripts to: [X] "Raise or lower windows"'''
Was this helpful to you? 2
Quote
the-edmeister
  • Top 25 Contributor
  • Moderator
5257 solutions 38862 answers

Chosen Solution

I pulled these prefs from a long defunct JavaScript extension when that extension was no longer compatible when a new version of Firefox came out. Probably goes back to before Firefox 3.0 or 3.5 - I just don't recall.

// advanced JavaScript Options:
user_pref("dom.disable_window_move_resize", true);
user_pref("dom.disable_window_open_feature.directories", true);
user_pref("dom.disable_window_open_feature.menubar", true);
user_pref("dom.disable_window_open_feature.personalbar", true);
user_pref("dom.disable_window_open_feature.scrollbars", true);
user_pref("dom.disable_window_open_feature.toolbar", true);

I have been carrying them forward via a user.js file for many years now, and that is the format used for prefs added in the user.js file. http://kb.mozillazine.org/User.js_file I use the user.js file to help me keep track of all the prefs that I commonly change in about:config for every new Profile that I create. One file to "drop" into a new Profile, rather then spends many minutes remembering and setting them all via about:config. I also do that with userChrome.css and userContent.csss files - the triumvirate of Firefox "user" files.

Type about:config in the URL bar and hit Enter. Paste this in the Search field at the top dom.disable_window_ and see all those hidden prefs (and a few more) as still being available in Firefox 57.

Sorry, I can't answer your 5 questions as there are too many variables involved with "new" and "open" actions for windows; and some are done via JavaScript which can affect how Firefox handles them. And as far as opening those in Tabs, the JavaScript links can "throw a wrench in the works" as to whether the user has control over if or how Firefox prefs can affect actions.

A far as an extension goes, I have no idea - but my guess is that it is doubtful, but don't let me dissuade you from looking for such an extension. Sorry that I can't help you more with specific answers for your 5 questions, but my "desire" for re-learning after changes to Firefox died back in the Firefox 3# versions, as API's were changed and the old API's became deprecated thru the 30's, 40's, and into the 50's versions. Still using ESR 38.0.5 and 47.0.1 where "signing" for extensions isn't mandatory. IMO, less "evil" and far safer with NoScript by using the older versions of Firefox, and better than switching to a different browser that wouldn't be as configurable and might have a steep learning curve. Stick with the "known evil" and avoid a new one that has a steep curve attached.

I am playing with Quantum a bit every day to learn what it is capable of and to learn what was "killed" as far as user configuration possibilities or options are concerned. But my goal for using Quantum as my primary browsers extends well into next year - maybe the Firefox 60 or 61 versions.

I pulled these prefs from a long defunct JavaScript extension when that extension was no longer compatible when a new version of Firefox came out. Probably goes back to before Firefox 3.0 or 3.5 - I just don't recall. <blockquote><pre><nowiki> // advanced JavaScript Options: user_pref("dom.disable_window_move_resize", true); user_pref("dom.disable_window_open_feature.directories", true); user_pref("dom.disable_window_open_feature.menubar", true); user_pref("dom.disable_window_open_feature.personalbar", true); user_pref("dom.disable_window_open_feature.scrollbars", true); user_pref("dom.disable_window_open_feature.toolbar", true); </nowiki></pre></blockquote> I have been carrying them forward via a '''user.js''' file for many years now, and that is the format used for prefs added in the user.js file. http://kb.mozillazine.org/User.js_file I use the '''user.js''' file to help me keep track of all the prefs that I commonly change in about:config for every new Profile that I create. One file to "drop" into a new Profile, rather then spends many minutes remembering and setting them all via about:config. ''I also do that with userChrome.css and userContent.csss files - the triumvirate of Firefox "user" files.'' Type '''about:config''' in the URL bar and hit Enter. Paste this in the Search field at the top '''dom.disable_window_''' and see all those hidden prefs ''(and a few more)'' as still being available in Firefox 57. Sorry, I can't answer your 5 questions as there are too many variables involved with "new" and "open" actions for windows; and some are done via JavaScript which can affect how Firefox handles them. And as far as opening those in Tabs, the JavaScript links can "throw a wrench in the works" as to whether the user has control over if or how Firefox prefs can affect actions. A far as an extension goes, I have no idea - but my guess is that it is doubtful, but don't let me dissuade you from looking for such an extension. Sorry that I can't help you more with specific answers for your 5 questions, but my "desire" for re-learning after changes to Firefox died back in the Firefox 3# versions, as API's were changed and the old API's became deprecated thru the 30's, 40's, and into the 50's versions. ''Still using ESR 38.0.5 and 47.0.1 where "signing" for extensions isn't mandatory. IMO, less "evil" and far safer with NoScript by using the older versions of Firefox, and better than switching to a different browser that wouldn't be as configurable and might have a steep learning curve. Stick with the "known evil" and avoid a new one that has a steep curve attached.'' I am playing with Quantum a bit every day to learn what it is capable of and to learn what was "killed" as far as user configuration possibilities or options are concerned. But my goal for using Quantum as my primary browsers extends well into next year - maybe the Firefox 60 or 61 versions.
Was this helpful to you? 2
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.