chrome and frame issues

SeRi@lDiE · 10-16-2011, 01:00 AM

I have an appliance that after a firmware update chrome refuses to render the page properly.

FireFox and Konqueror (With Agent String for FF 3.0.5) work just fine

Looking at the source of the page I got this error.

Code:


<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>VoIP Web Management</title>

</head>
<frameset framespacing="0" border="0" frameborder="0" cols="220,*">
        <frameset rows="90,*">
          <frame name="Top" src="logo.htm" target="Top" scrolling="no" noresize>
                <frame name="left" src="choice.htm" target="left" scrolling="auto" noresize>
        </frameset>
        <frame name="right" src="info.htm" scrolling="auto" noresize target="right">
        <noframes>
        <body>
        <p>This homepage use frames but your browser does not support it.</p>
        </body>
        </noframes>
</frameset>
</html>

Is there a way to enable frame support in chrome? I have try serveral experimental chrome extensions that allow you to define user agents but it did not work as good as konqueror...

Any help is appreciated!
TIA.

SeRi@lDiE · 10-16-2011, 01:12 AM

Well I updated google chrome to the latest version which is 14.0.835.202 and the update seem to brake the agent string specified in the .desktop file under EXEC=
no matter what you put there it does not work....

SeRi@lDiE · 10-16-2011, 01:22 AM

I got EXEC= to work but no frames yet...

hen770 · 10-16-2011, 02:38 AM

Is it just a specific page? Or every page that you are trto load?

Is that page was able to load before the firmware update?

SeRi@lDiE · 10-16-2011, 09:28 AM

Quote:

Originally Posted by hen770

Is it just a specific page? Or every page that you are trto load?

Is that page was able to load before the firmware update?

To my knowledge is just this page and yes before the firmware update it work just fine.

neymac · 10-16-2011, 10:35 AM

This page works with Opera web browser, but doesn't work with google-chrome 15.0.874.92 beta, konqueror, rekonq nor with Firefox-7.0.1 that I use.

PS:
After create files choice.htm, info.htm and logo.htm, it worked with all web browsers above.

SeRi@lDiE · 10-16-2011, 11:31 AM

Quote:

Originally Posted by neymac

This page works with Opera web browser, but doesn't work with google-chrome 15.0.874.92 beta, konqueror, rekonq nor with Firefox-7.0.1 that I use.

PS:
After create files choice.htm, info.htm and logo.htm, it worked with all web browsers above.

neymac,

Where did you created this files?
I am talking about an appliance. To be exact is a PROTech MV-370 GSM Gateway.
Do you have the same issue?

Thanks!

neymac · 10-16-2011, 03:49 PM

Quote:

Originally Posted by SeRi@lDiE

neymac,

Where did you created this files?
I am talking about an appliance. To be exact is a PROTech MV-370 GSM Gateway.
Do you have the same issue?

Thanks!

No, Sorry, I misunderstood.

SeRi@lDiE · 10-17-2011, 11:04 AM

neymac,

Not a problem. Thanks for the help.

Any body else out there?

vulcan59 · 10-17-2011, 01:24 PM

Does this appliance provide a DOCTYPE header at the start of the HTML? Just curious because the HTML you provided throws up errors at http://validator.w3.org no matter which doctype I choose. I don't use Chrome but I just wonder if it is a bit more pedantic about syntax than the other browsers.

SeRi@lDiE · 10-17-2011, 11:35 PM

Thanks for the help vulcan59,

It does not have a DOCTYPE in the header....

What I am puzzled about is that it works ok with FF and if I use konqueror with an agent string of FF it works as well...

In chrome not matter what agent string I use it does not work...

vulcan59 · 10-18-2011, 06:13 AM

The web server may be using the agent string to customize the HTML it outputs but it is still up to the browser to interpret that HTML and display it. I still think there may be something about the HTML which Chrome doesn't like. Did the firmware upgrade break this? Was the HTML different before the firmware upgrade and did it used to work with Chrome? If it worked with Chrome before the firmware upgrade but doesn't now then I would be asking the firmware supplier about this.