Could you link to the site that has this problem so a volunteer could see it live?

If the site isn't up yet, it might be possible to create a test case on http://jsfiddle.net/ or a similar site.

You can try to reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

• Hold down the Shift key and left-click the Reload button
• Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
• Press "Command + Shift + R" (Mac)

Upon further testing it is not just the CSS 3 menu. It is any link within my website that uses the target="main" tag. The menu is a top frame that is always there for navigation within my website. This web page is simple and straight forward with very little complex coding. Targeting was working correctly in version 30 but version 31 broke it. IE 11 with the latest updates and Chrome latest version still work fine. Index.html breaks page into 3 frames with one designated name="main". Small frame at the top is the menu and directs other pages within my website to target="main" and outside my website to target="_top". Pages directed to my main frame now opens in a new tab instead of the main frame and does it the same on any computer updated to FF v31.

Are these ordinary hyperlinks or does a script set the src of the main frame?

If you are sending a relative URL to the frame (protocol and host name omitted), could you test whether sending a full URL bypasses the problem?

It is an ordinary hyper link being sent to a named window. This is the same html protocol used since Netscape 2.0 added frames to the browser. typically what is happening: even though the initiating document has a name="main" command in it Firefox 31 does not remember it and performs the default action. When there is no frame with that particular name the new document will be opened in a new tab or window from the top. Foxfire 30 will render the page correctly and also current Chrome, IE11, and others. All computers on windows 7 x 64 and 32 bit, and an XP 32 unit developed the same glitch when updated to FF31.

Use of a full url does nothing different but still works in other browsers.

I created a simple frameset for testing and do not see the problem here in Firefox 31: http://dev.jeffersonscher.com/frame/

Is there a critical difference I'm overlooking between my example and your page?

Problem still exists. Your test page did work for me but my page setup is similar to yours but would not work. Nothing has changed with my web page until I ran my tests. FF31 and now the latest Chrome are not loading my page correctly. IE 11 still works correctly. All browser caches have been flushed and still no luck.

Did you check the Web Console (Firefox/Tools > Web Developer) for error messages?

• https://developer.mozilla.org/Tools/Web_Console

Can you post a link or a reduced code example with this issue?

I have a test file and it works fine in IE11. I will see Tuesday if Microsoft made any real changes FF31 and Chrome now are not targeting frames. They simply do not remember name="main" from the initiating file and perform the default action of starting the targeted file in a new tab. FF31 does not target one frame from another in any form from any computer I have access to on my web page. It does not do it even from a standard hyperlink using the target= "" command. This is simple coding with no errors. Something new in Firefox is blocking this function that was not in FF30. What is the new function and can it be disabled or modified? There is no indication in the Console of an error in any way and the only thing it shows is when a page is called with one of the four default targets but not a named one.

Hi davids85220, I thought you said my test page works for you.

Can you post a link to your page or test file which is not working? Otherwise, we can't determine what is different, and whether that leads to a suggestion to change your code or uncovers a bug in Firefox and Chrome.