Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Firefox version 89.0.1 is not handling frameset src. No redirection to src

  • 8 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan rjpool

more options

Firefox version 89.0.1 is not handling frameset src. No redirection to src.

This code is generated by my ISP's domain name frame forwarding software so I have no access to how it is generated ie: I am in no position to use iframes.

I should point out that this worked last week no problem. I had my settings on auto update so maybe an update has broken this I don't know.

Below is the code. It works fine in Chrome, MS Edge, Safari and Opera. Which tends to suggest that Firefox is the problem.

Note that this is exactly what I see when I view the page source in Firefox. There is a frame tag commented out. I don't know whether that is how it came from the ISP's server or whether Firefox has commented it out on receipt.

How do I get around this?

Ray Pooley

[CODE] <meta http-equiv="<a target=">Content-Type" content="text/html; charset=windows-1252"> <meta name="<a target=">description" CONTENT=""> <meta name="<a target=">keywords" CONTENT=""> <title></title> <frameset rows="<a target="_blank">100%,*" frameborder="0" border="0" framespacing="0" marginwidth="0" marginheight="0"> <frame frameborder="<a target="_blank">0" name="MYTOPFRAME" src="view-source:http://waterlooplace.dyndns.org:90/" target="_blank">http://waterlooplace.dyndns.org:90" noresize="noresize"> <noframes>

If you see this your browser does not support frames

Click here to go to http://waterlooplace.dyndns.org:90

</noframes> </frameset> /CODE

Firefox version 89.0.1 is not handling frameset src. No redirection to src. This code is generated by my ISP's domain name frame forwarding software so I have no access to how it is generated ie: I am in no position to use iframes. I should point out that this worked last week no problem. I had my settings on auto update so maybe an update has broken this I don't know. Below is the code. It works fine in Chrome, MS Edge, Safari and Opera. Which tends to suggest that Firefox is the problem. Note that this is exactly what I see when I view the page source in Firefox. There is a frame tag commented out. I don't know whether that is how it came from the ISP's server or whether Firefox has commented it out on receipt. How do I get around this? Ray Pooley [CODE] <html> <head> <meta http-equiv="<a target="_blank">Content-Type</a>" content="<a target="_blank">text/html; charset=windows-1252</a>"> <meta NAME="<a target="_blank">description</a>" CONTENT="<a target="_blank"></a>"> <meta NAME="<a target="_blank">keywords</a>" CONTENT="<a target="_blank"></a>"> <title></title> </head> <frameset rows="<a target="_blank">100%,*</a>" frameborder="<a target="_blank">0</a>" border="<a target="_blank">0</a>" framespacing="<a target="_blank">0</a>" marginwidth="<a target="_blank">0</a>" marginheight="<a target="_blank">0</a>"> <frame frameborder="<a target="_blank">0</a>" name="<a target="_blank">MYTOPFRAME</a>" src="<a href="<a target="_blank">view-source:http://waterlooplace.dyndns.org:90/</a>" target="_blank"><a href="http://waterlooplace.dyndns.org:90" target="_blank">http://waterlooplace.dyndns.org:90</a></a>" noresize="<a target="_blank">noresize</a>"> <!-- <frame name="defo098dsfwwerkmnn8908" src="<a href="http://waterlooplace.dyndns.org:90" target="_blank">http://waterlooplace.dyndns.org:90</a>" frameborder="no" framespacing="0"> --> <noframes> <body> <div align="center">If you see this your browser does not support frames<P> <A href="waterlooplace.dyndns.org:90">Click here to go to <a href="http://waterlooplace.dyndns.org:90" target="_blank">http://waterlooplace.dyndns.org:90</a></A> </div> </body> </noframes> </frameset> </html> [/CODE]

Alle antwurden (8)

more options

I have just reviewed the above question and noticed that commented out frame tag that I referred to in the question has been stripped out of the code I posted by the the software on postback.

So here is an image of the code showing the commented out tag.

Cheers

Ray Pooley

more options

Are there any errors in the console, referring to this issue?

more options

Thanks for your response.

No. There are no error messages. The response from my ISP is being delivered to the browser correctly. The other browsers process that response correctly and redirect the browser to the location defined by the frame src attribute. So ther are no errors. You can see the response code in full in the page source image that I posted in my previous posting. The problem is that Firefox isn't processing the frameset. It is not redirecting the browser to the location defined by the src attribute.

Cheers

Ray Pooley

more options

Can't reproduce this issue. Everything seems to be OK on my side.

more options

Hi TyDraniu

What version of FF are you running? It could be a recent auto update tghat has broken this.

Cheers

more options

Update:

I have just uninstalled and reinstalled FF 89.0.1 and it is now redirecting as it should.

I have no idea why it spontaneously went from working to not working.

So if any one else has this issue you could try that. It fixed my issue.

Cheers

Ray Pooley

more options

I'm pretty sure that it would be enough to clear the cache, as they commented out a frame and add a new one. Something went wrong and you've been left with an outdated frame address in cache...

more options

Perhaps.

Cheers.