Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

Opens new tab instead of changing page within a frame.

  • 5 ŋuɖoɖowo
  • 4 masɔmasɔ sia le wosi
  • 1 view
  • Nuɖoɖo mlɔetɔ divelink

Mr_Fred
Mr_Fred
more options

V 22: When I open site with frame header & left navigation home page is fine. When I click to navigate to different page, frame header & navigation buttons are gone. Only content of new page is displayed. Site is control page for access point on network. IE and Chrome work just fine.

This is new behavior. Started after update to Release 22.0

V 22: When I open site with frame header & left navigation home page is fine. When I click to navigate to different page, frame header & navigation buttons are gone. Only content of new page is displayed. Site is control page for access point on network. IE and Chrome work just fine. This is new behavior. Started after update to Release 22.0

All Replies (5)

finitarry
finitarry
more options

Did you accidentally switch to full screen mode? Pressing the F11 key will toggle that mode on Windows.

Mr_Fred
Mr_Fred Biabia la
more options

No, not in full screen mode. First tab gives me page correctly. Clicking on different button used to give me info within frame. Now I get new tab created without header and left navigation buttons.

Mr_Fred trɔe

the-edmeister
the-edmeister
  • Moderator
more options

So your issue is related to a Router "web page"?

Mr_Fred
Mr_Fred Biabia la
more options

Access Point that connects to router. This is a browser thing, AP works fine. Just now opens a new tab instead of updating the home tab which it used to do.

divelink
divelink
more options

Hi, I have the same problem. After checking settings and add-ons, I discovered that the add-on for Dragon Naturally Speaking seemed to be causing the problem. Probably a feature of DNS. When I disabled the DNS add-on, Firefox behaved correctly.