Closed Bug 358187 Opened 18 years ago Closed 16 years ago

Bad merge of tab/window prefs can lead to Options UI showing wrong setting

Categories

(Firefox :: Settings UI, defect, P4)

Product:
Firefox
Component:
Settings UI
Version:
2.0 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INVALID
Milestone:
Firefox 3 beta3

People

(Reporter: nthomas, Assigned: mgalli)

References

(
URL
)

Details

(Keywords: relnote, Whiteboard: Work around in comment #13)

This came up in #firefox, from a user who prefers windows to tabs. They found that target="_blank" links were opening in new tabs in Firefox 2, despite the UI saying they would open in a new window. They'd previously had this set up to their satisfaction in 1.5.0.x, and weren't using any extensions. Steps to reproduce: 1, Create a new profile with Firefox 1.5 2, Set "Open links from other apps" to new window, and "Force links to open ..." to new window 3, verify that the images at the URL load in new windows 4, load profile with Firefox 2 5, click on images again Expected results: Image loads in new window Actual results: Image loads in new tab, but UI shows "new window" for Options:Tabs:"New pages should be opened in" I haven't looked at other combinations of those prefs, or other link scenarios.
I had the same problem. The UI setting didn't match what I saw in about:config. I fixed it by changing from "a new window" to a "new tab" and then back again.
*** Bug 358184 has been marked as a duplicate of this bug. ***
*** Bug 358411 has been marked as a duplicate of this bug. ***
so, is there a solution? someone named ispiked@gmail seems to think a key called browser.link.open_newwindow needs to be set to 3, but he's not real clear on where to find it. it's not in the registry, there are no files called about:config, nor are there any files called config containing the phrase browser.link.open_newwindow.
*** Bug 358521 has been marked as a duplicate of this bug. ***
In response to #4: You may have found this out by now, but just type about:config in the urlbar of Firefox (where you usually see http:// addresses)
*** Bug 359364 has been marked as a duplicate of this bug. ***
*** Bug 360091 has been marked as a duplicate of this bug. ***
*** Bug 364253 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > I had the same problem. The UI setting didn't match what I saw in > about:config. I fixed it by changing from "a new window" to a "new tab" and > then back again. > WORKS AGAIN. THANK YOU. MARC E KORMAN
This is true for GranParadiso (3.0a1) also, and the fix of changing the setting and back works there as well.
I can confirm the bug as well, but the "fix" from James Arnold has to be done for every session. Once you restart Firefox the bad behavior shows up again.
(In reply to comment #12) > I can confirm the bug as well, but the "fix" from James Arnold has to be done > for every session. Once you restart Firefox the bad behavior shows up again. > Actually, FOR ME, my changing the UI setting from OPEN IN NEW WINDOWS to OPEN IN NEW TABS and then back again fixed the bug PERMANENTLY. Marc E Korman
Same here. I only had to use the work-around once, and the problem disappeared permanently.
Blocks: 364660
Blocks: 364595
Somebody marked this as resolved but it is not or else at least 18 people who cared enough to report the bug wouldn't have posted about it. I have had to do the preference workaround several times therefore the issue is not resolved. Maybe there so many "duplicate" postings about this bug because it has NOT been resolved!
(In reply to comment #4) > so, is there a solution? someone named ispiked@gmail seems to think a key > called browser.link.open_newwindow needs to be set to 3, but he's not real > clear on where to find it. it's not in the registry, there are no files called > about:config, nor are there any files called config containing the phrase > browser.link.open_newwindow. > "browser.link.open_newwindow needs to be set to 3" is the setting for tabs. The issue is that we didn't want tabs. It needs to be set to 2 if you want a new window.
(In reply to comment #19) > Somebody marked this as resolved but it is not or else at least 18 people who > cared enough to report the bug wouldn't have posted about it. I have had to do > the preference workaround several times therefore the issue is not resolved. > Maybe there so many "duplicate" postings about this bug because it has NOT been > resolved! I see "NEW" for the status. Where do you see that it's been marked as "resolved"?
This seems to be a pref migration problem. Noming for Fx3, but if we can get it for a branch release as well, that'd be nice.
Flags: wanted1.8.1.x+
Flags: blocking-firefox3?
(In reply to comment #22) > This seems to be a pref migration problem. Noming for Fx3, but if we can get it > for a branch release as well, that'd be nice. > Just want to agree with the pref migration problem diagnosis after having experienced this bug on all three installations I've upgraded from 1.5 to 2. The workaround does fix it but it's not trivial and having target="_blank" links open in tabs can be quite frustrating.
Flags: blocking-firefox3? → blocking-firefox3+
Target Milestone: --- → Firefox 3 beta1
Having read through this bug blog, I am not sure whether or not my issue is the same (and I'm not sure whether any of the issues are resolved!) I want all clicked browser links etc always to open in nnew tabs within the one window. This was always (for me) one of the greatest advantages of Firefox, alongside better security, over IE. Having upgraded to Firefox 2.0.0.4 (and today checked for updates - none), despite trying every combination of options I can think of (and changed them back and forward several times within and between sessions!) this now seems to be unobtainable. Furthermore, there seems mto be no obvious logic to which links open in new windows, which in new tabs and which over-write an existing tab. The last of these is the most irritating of all ... having run a Google search, the last thing I want to happen is to click one of the resultant linkls only to have it replace the search results ... anfd then to have to 'close' the new webpage in order to go back to the search results! Any help would be much appreciated!
In my case 2.0.0.4 it always opens in TAB. This is a most serious limitation of the browser and a fix should have highest priority IMO. It is not about TABS versus windows; sometimes you want one method or the other. Opening in a new window is essential if you want to compare web pages side by side, as is convenient with a wide screen monitor. Tabs are useful for remembering a trail of web pages. Let us at least have the choice.
Ok, so you marked the bug I reported (386523) as duplicate even though I did a search and didn't find it, but what's the fix? Marking the bug duplicate and not conveying the fix to the person that reported the problem is utterly useless. So what is the fix?
Curt, see comment #13.
Whiteboard: Work around in comment #13
Thanks! Comment #1 too. That corrected it.
I've switched from windows preference to tabs and back to windows and that didn't fix it. Sorry for my ignorance, but what does "UI" stand for and is this somewhere other than in the preferences options? Cliff
UI is user interface
Assignee: nobody → gavin.sharp
Target Milestone: Firefox 3 M7 → Firefox 3 M9
To clarify comment #0, I can reproduce if step 2 is changed to 2, Set "Open links from other apps" to "new window"
Target Milestone: Firefox 3 M9 → Firefox 3 M10
Target Milestone: Firefox 3 M10 → Firefox 3 M11
Priority: -- → P4
Assignee: gavin.sharp → mgalli
Flags: wanted-firefox3+
Flags: blocking-firefox3-
Flags: blocking-firefox3+
I have run into this on a "new" openSUSE 11.0 installation with a "new" Firefox profile; so it's not really a migration issue... Defaults were: browser.link.open_external;2 browser.link.open_newwindow;3 browser.link.open_newwindow.restriction;2 For correct operation needed value is: browser.link.open_newwindow;2
This would be fixed by bug 324164.
Depends on: 324164
Resolving this bug as INVALID since with bug 324164 being fixed, there no longer are two prefs sharing the same UI setting.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.