The iframe is back

[jscheuer1]

One other thing. In Chrome, probably all web kit, if the files are on the same domain, and scrolling="no", the iframe has no scrollbars. Using only overflow: hidden; as style for the iframe doesn't work. So something is perhaps wrong with all the browsers here. This worked with the scripted method as well as using the hard coded attribute.

[traq]

I think iframe is one of the newer elements in html5 - IIRC, it was originally excluded from the spec, but was returned because 1) it works in all browsers and 2) there's no good replacement for the functionality. It makes sense that support for the html5 attributes (like "seamless" and using css instead of the scrollbars attribute) would be dodgy.

[jscheuer1]

The iframe is back (HTML5). After all the trouble I had finding a proper replacement for it (HTML4 strict).

I think iframe is one of the newer elements in html5 - using css instead of the scrollbars attribute) would be dodgy.

Almost back then.

And perhaps the fox is the only one that got it right after all.

Why shouldn't you be able to control the scrollbars with style regardless of where the page in the iframe comes from? You cannot change its content or scroll it (well you can scroll it with a nested full page iframe), without server side code to capture the page and make it your own.

[traq]

Why shouldn't you be able to control the scrollbars with style regardless of where the page in the iframe comes from?

I would assume it was a bit of the "same-domain" logic on the part of the vendors; I guess the scrollbars would be considered part of the imported page. The inconsistency probably means that it's one of those things that wasn't very clear in the earlier specs.

HTML5 is fairly "solid" now, on paper. But most browser support for html5 is either carryover from html4.01 / xhtml1.1, or something that vendors developed themselves and has now been "rolled into" the spec.