×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.





While iframes are part of HTML5, there are several security warnings in
the W3C recommendation.


Kelly,

Most of the warnings appear to be related to disabling the <iframe>'s
sandbox. Others are related to malicious content which might be referenced
from say hidden <iframe>s. I don't see a problem with using them to
reference content on a trusted site.

Hopefully own's own site is trusted; though that may depend on whether
someone creates or downloads or stores trojan-horse type spoofs hiding
malicious code.

Malicious code is not really an <iframe> issue, however. In fact, an
<iframe>'s sandbox may actually protect against it, as indicated in the
blog which you referenced.

I use <iframe>s as a simple solution for "responsiveness"; just refresh
<iframe> content rather than a whole page. And that doesn't preclude one
from just refreshing part of an <iframe> page asynchronously.

I like that the size of an <iframe> can be fluid; adjusting automatically
to screen size. I just treat them as one tool in the box.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.