Reputation: 50662
I would like to create an <iframe>
on the page, but then add the src
later. If I make an iframe without an src
attribute, then it loads the current page in some browsers. What is the correct value to set for the src
so that it just loads a blank iframe?
The answers I've seen are:
about:blank
javascript:false
javascript:void(0)
javascript:"";
Is there a clear winner? If not, what are the tradeoffs?
I'd like to not have mixed content warnings for HTTPS urls, nor any back-button, history, or reload weirdness in all browsers from IE6 onward.
Upvotes: 25
Views: 35165
Reputation: 1
I run into this line of code:
iframe.setAttribute("src", "javascript:false");
as well. I wanted to remove javascript:URL
.
Found this note from the Web Hypertext Application Technology Working Group [Updated 2 October 2019]
The otherwise steps for iframe or frame elements are as follows:
If the element has no src attribute specified, or its value is the empty string, let url be the URL "about:blank".
Upvotes: 0
Reputation: 14049
javascript:false
:
IE10 and FF (checked in v23 in Linux) will show 'false' as content.
javascript:void(0)
&& javascript:;
:
IE will show 'cannot display the webpage' error in the iframe. Also, when setting the src from a valid url to javascript:void(0)
, the page will not get blank.
about:blank
:
Works in all browsers but IE 9 sends an request to the server with path "null". Still the best bet IMO
Checkout http://jsfiddle.net/eybDj/1
Checkout http://jsfiddle.net/sv_in/gRU3V/ to see how iframe src changes on dynamic updation with JS
Upvotes: 3
Reputation: 28096
As I posted in this question: Is an empty iframe src valid?, it looks acceptable to just leave out the src=
attribute completely.
Upvotes: 1
Reputation: 11
javascript:false
works in modern browsers.
What I've seen is that this only "fails" when dumb spiders try to load javascript:false
as a page.
Solution: Block the dumb spiders.
Upvotes: 1
Reputation: 11
Yes, I know I'm reviving an old thread. Sue me. I'm interested in the answer.
I don't understand why having the trigger being a form submit precludes dynamically creating the IFrame. Does this not do exactly what you want?
<html>
<head>
<script type="text/javascript">
function setIFrame(elemName, target, width, height) {
document.getElementById(elemName).innerHTML="<iframe width="+width+" height="+height+" src='"+target+"'></iframe>";
}
</script>
</head>
<body>
<div id="iframe" style="width:400px; height:200px"></div>
<form onSubmit="setIFrame('iframe', 'http://www.google.com', 400, 200); return false;">
<input type="submit" value="Set IFrame"/>
</form>
</body>
</html>
Upvotes: 0
Reputation: 449803
Re your comment clarifying that you're planning to use the iframe as the target for a form submission:
I would use an empty document on the server that sends back a 204 no content
.
It avoids
javascript:
protocol It's also valid HTML.
So what if it generates an extra request? Set the caching headers right, and there will be only one request for each client.
Upvotes: 6
Reputation: 110
Standard approach when creating an "empty" iframe (as an iframe shim, for example), is to set the src as javascript:false;
. This is the method used by most of the JavaScript libraries that create iframe shims for you (e.g. YUI's Overlay).
Upvotes: 7
Reputation: 36557
Not sure if all browsers support "about:blank", so I'd just go with your own blank page then.
Another idea: Why not add the whole iframe using javascript instead of just the src?
Upvotes: 10
Reputation: 17994
IMO: if you don't put the src, your page won't validate. But's about it. If you put a src="", your server will log many 404 errors.
Nothing is really wrong as in "damaging". But then, is it actually not wrong to use an iframe in itself?
°-
Upvotes: 0