Vincent Pollard wrote:
> html #IDNameofIFrame html { overflow-y: auto !important; }
> It is legal in css2.1 to write html html like this?
Legal, yes, but such a selector chain doesn't point to any element since
there's no 'html' element inside 'html'. Selector chains can only
express parent --> child relations, not the other way round.
This would make sense selector-wise, but won't affect an iframe in a page:
html {
overflow-y: auto !important;
}
...so, if #IDNameofIFrame is the iframe, make it...
html #IDNameofIFrame {
overflow-y: auto !important;
}
> It's hard to find help online as 'html' brings up too many references
> to the language, instead of the element.
You can always check validity/legality here...
<http://jigsaw.w3.org/css-validator/#validate_by_input>
...but "valid" doesn't necessarily mean that it will work. Valid/legal
selector chains are easy to build up, but unless they address the exact
structure of your document at markup level they'll be nonsensical and
have no effect whatsoever.
Can't offer more help than that without seeing the actual document with
the iframe - and the problem, with the iframe's content loaded. Iframes
are somewhat uncontrollable - no real cross-browser support for anything
but the basic styling, and you can not address the document loaded into
the iframe through the iframe.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
