This could be a related to the several "Force links..." into tab bugs, but no one has mentioned any problems when forcing links into the current window/tab. Steps to reproduce: 1) Set "Force Links..." to open in the current window/tab. 2) Visit http://www.niho.com/forsale/detail2.asp?prop=241 and click on a map picture. The website is cleared and the JS console spits out: "Error: uncaught exception: Permission denied to get property ChromeWindow.document" I can see this problem on a couple of websites (cnn.com for example). Personally, I think it might be a good idea to load chromeless windows normally (browser.link.open_newwindow.restriction = 3) when the user has selected to load links that open new windows in the current tab/window. Additionally, I think this would be the most intuitive to the end user - in most cases pop-up windows should not steal the page (consider opening up an address book in a webmail site, logging into a bank, or, worst case scenario, turning off the pop-up blocker). This could also be a potential dataloss situation.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → DUPLICATE
Thanks DanM. I wasn't sure if they were the same bug, since the code was slightly different. Also, I didn't mean for the bug to expand over multiple problems. Whenever I post a bug I always try to post a potential solution and not diverting chrome less windows was the best solution I could think of. You are also correct about restriction=2, 3 was a typo and setting it to 2 does fix a lot of these problems.
You need to log in before you can comment on or make changes to this bug.