But...
 
If you think about it "theme" does imply look and feel for a document or the ability to change it.  So a CSS in a theme file should be all inclusive.
 
Now..
 
Back to the "rock"!
----- Original Message -----
Sent: Saturday, January 20, 2001 5:42 PM
Subject: Re: [Dynapi-Help] (style)

>New to the game I find that netscape doesn't apply any of my styles from a linked stylesheet to text within nested layeers, I then tried >an inline style tag and that worked for simple layers but failed when using setHTML method
I think this happens when you have included more than one external stylesheets into the doc. I you are using a "skin" widget, it includes a stylesheet by default when declaring "theme", when including a second stylesheet of my own NS stopped responding.
 
 
Cheers,
Richard Bennett
 
[EMAIL PROTECTED]
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
----- Original Message -----
Sent: Sunday, January 21, 2001 2:14 AM
Subject: RE: [Dynapi-Help] (style)

New to the game I find that netscape doesn't apply any of my styles from a linked stylesheet to text within nested layeers, I then tried an inline style tag and that worked for simple layers but failed when using setHTML method - I've resorted to the deprecated font tag. In a similar vain netscape 4.7 doesn't decode character and language settings from the meta tag when the text is in DynLayers ( namely Central European, lang=pl). I've previously used inline layers without character problems.
blessings Darryl
 Richard wrote: 

Not really, you can include one normally like this:
 
<link rel='stylesheet' type='text/css' href='spec.css' />
 
or with a document write in the beginning of the document, or you can access some css properties directly for a layer after creation like this:
myLayer.css.padding="4px" 
 
although not all css attributes are available in all browsers.
 
Now if you are using any of the "skin' widgets, the line:
document.write('<script language="Javascript" src="'+theme+'style.js"><'+'/'+'script>');
actually includes a .css file from the theme directory, and this can give problems with conflicting names if you include a second yourself.
 
Of course you can just put a little inline css in the head as well:
<style>blah</style>
 
Cheers,
Richard  :o
 

Reply via email to