cannot execute html frameset files in chrome

[Rathan Reddy Kasam]

hi,

I cannot execute the following frameset .html files only in chrome, while I  run these files in all other browsers they execute well.. when I saved these files in local  "D drive" with .html extension the issue is coming.Frameset ParentNode is not working, while we call from the inside HTML page of that frame. 

[PhistucK]

You can upload the files to GitHub or GitHub Gist. Without reproducing the issue and seeing the actual code, it is hard to provide proper support here.

Generally, you should not use file:// URLs, because they have different, non-interoperable restrictions in every browser. Some allow them almost everything, some allow them almost nothing and some allow them some things. It is best to use a lightweight static server instead.

Also, framesets are obsolete at this point, you better modernize your files anyhow (this does not mean it will resolve your problem if you still need <iframe> and the like, but still).

☆PhistucK

On Fri, Aug 11, 2017 at 8:57 AM, Rathan Reddy Kasam <rathanre...@gmail.com> wrote:

hi,

I cannot execute the following frameset .html files only in chrome, while I  run these files in all other browsers they execute well.. when I saved these files in local  "D drive" with .html extension the issue is coming.Frameset ParentNode is not working, while we call from the inside HTML page of that frame. 

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

[PhistucK]

​Note - when I suggested that you upload it to GitHub or GitHub Gist, it is because one of your queued posts​ said that you could not upload the file to the group. Sorry if that was not clear. I was definitely not suggesting that you upload any local file to GitHub. :)

Anyway, in order to reproduce the issue, it would be great if you made the files available online publicly somehow (GitHub is just one of the simple ways, plnkr.co is another simple way).

☆PhistucK