Closed Bug 228703 Opened 21 years ago Closed 21 years ago

Would like a way to freeze a window even when supportDDEExec is true

Categories

(Firefox :: General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: shankarunni, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031203 Firebird/0.7+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031203 Firebird/0.7+ I'm caught between two conflicting desires: There are some windows that I do not want to be hijacked when I click on links in other programs (because they are showing something important that I'm working on). At the same time, I'd rather not set supportDDEExec to false, and have a fresh window pop up each time and clutter up my desktop (and bloat Firebird). It would be really nice to have a "View" option to "freeze" a window (i.e. make it immune to being hijacked by DDEExec). When a DDE request comes in, FB should pick one of the windows that do *not* have this freeze flag set (but otherwise using whatever algorithm it uses now for which of those windows to pick). It should open a new window if there are no such windows. There's no need (that I can see) to make this persistent in any fashion (e.g. remember a per-site preference for this flag, or anything like that). A purely transient flag is enough. Reproducible: Always Steps to Reproduce: 1. Set user_pref("advanced.system.supportDDEExec", true); 2. Bring up an important page, among a bunch of other windows. 3. Click on a URL in an external app. Actual Results: 1. Watch the window with the important page being hijacked :-). Expected Results: 1. Some way to set a flag on that Window in the View menu, perhaps, to prevent this hijacking of just that one window.
maybe it would be okay as an extension, but this is far too arcane for the core design by far
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
QA Contact: mconnor
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.