User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14 after a href to an external site opening in the same window (tab) clicking a menu option of the site the page will open in a new tab and the menu is disappeared. The page should appear in the same tab in a iframe and keep showing the menu. This works fine in ff3.0, but fials to do so in ff3.5. You can use the url www.weespweggeluid.nl, go to LINKS, select a external link, if the extrnal page shows in the iframe select a page from the menu e.g. NIEUWS. The site is in dutch, but the problem will be clear. If you need more information of html or php code I can provide you with them. Reproducible: Always Steps to Reproduce: 1.open site www.weespweggeluid.nl 2.select LINKS from the menu 3.select a external link 4.select NIEUWS from the menu 5.the news page should show in the iframe with the menu but does show in a new tab withouth the menu 6.do this in ff3.5 and repeat it in ff3.0 to see the difference Actual Results: page shows in new tab instead of the same tab in the iframe Expected Results: should display the page in the same tab in the iframe
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.