(In reply to comment #1) no it wasn't checked, but checking it (also with restart) didn't make it work. btw. i'd rather see settings like allow/forbid "Raise or lower windows" being URL depended such loading of images is. there are applications like the given mapping example that are both extensive in loaded data and use of AJAX that do not fit in a classical history back/forward schema. here is a new windows a solution. but not if focus cannot be set when it is forbidden for spaming content (what's a good idea)
A minimized testcase that demonstrates the bug would be great.
Assignee: nobody → general
Component: Tabbed Browser → DOM
Product: Firefox → Core
QA Contact: tabbed.browser → ian
Version: unspecified → 1.8 Branch
Created attachment 242963 [details] page 1 for testing tab opener.focus() needs page2.html in order to work.
Created attachment 242964 [details] page 2 for testing tab opener.focus() needs page1.html in order to work.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Do you have new "pages" set to open in tabs or windows? This works fine for me when I set the "New pages should be opened in a: new window" preference and enable windows to be lowered or raised. When I have them set to open in new tabs, a new tab is opened when I click the link in page1.html and when I click the link in page2.html the page1.html tab seems to reload, but it's not focused. This happens both with the "Raise or lower windows" preference is enabled. FWIW, 1.5 was shipped with the "Raise or lower windows" pref. enabled by default, whereas 2.0 and current trunk have this disabled.
OS: Windows XP → All
Hardware: PC → All
> Do you have new "pages" set to open in tabs or windows? i have the 2.0RC3 default, that is open in new tab. > When I have them set to open in new tabs, a new tab is opened when I click the > link in page1.html and when I click the link in page2.html the page1.html tab > seems to reload, but it's not focused. This happens both with the "Raise or > lower windows" preference is enabled. yes, that's it and that is the problem from my point of view. what is it worth to be able eo talk to a win/tab (the win/tab #1 effectively loads a new url) and not being able to bring it to the foregroud?
See bug 292314.
Regression from bug 310825?
Yes! This bug is very much a regression from bug 310825 (and i have no idea how to make that hyper link...).
You need to log in before you can comment on or make changes to this bug.