iframe

For that matter, just make browsers not allow an iframe within another iframe...

We'll insert an iFrame into the page and then insert their JS into the iFrame, which will then load the one ad to display.

It probably means accessing another contexts' global object directly via an iframe (or child window), which works for matching domains and throws a security exception otherwise.

The sandboxing for an external script you want already is feasible with an iframe with a different origin.

From TFA: and loading posts in an <iframe> gives the opportunity to display content while the user waits.

You'd have to write the ad code into the iframe from the outer page, but that's not hard.

Just tested img and iframe and they work quite happily from the web to the local network.

When they visit Person B's site the include an iframe for the share endpoint at personident.com.

Usually the script (and ad) is in an iFrame, so that makes it slightly better.

Does it have to have a different domain or would a `src`-less iframe also work?

Is it ok to embedded this (and the full Iceland map) with an iframe?

Aparently their main page loads HN as an iframe and hides all techcrunch stories.

If you're going to put adverts on your site, always put them within an iframe, pointed at a separate "adverts" only domain.

We self hosted some, but one of the things we "self hosted" was an iframe to an ad network.

“[...]use several gigabytes of RAM, even when just displaying document-like content” might also be rooted in advertisers packing megabytes of rubbish in an iframe or web devs loading tons of unneeded web fonts.

Iframe JS can run in multiple threads if engineered right.