Web designers - css question.

[Big Dave]

So I spend most of last night getting my head around cascading style sheets. 'the way forward' people I respect tell me. Skinny code for nifty effects. The light side.

OK - I'll get away from the surplus nested tags and messy litter that dreamweaver can create and use a mix of html styles and css and go back to manually coding a lot of www.kiwirider.co.nz

All works fine except when i test it in netscape - no dice on the navigation effects.
Any of you guys have experience with this - i see there are a few different protocols for calling up the .css. Any that work with netscape that you know of?

[SPORK]

Off topic, but did you know that one of the directors/important people for Futurama is David X. Cohen? It's true. Watch an episode (7:00pm C4)

[SpankMe]

Writing CSS code that works in both IE and FF is a complete fucking pain. Found that out when do my personel page. (http://spankme.dynu.com/) Which is why I gave up on back when Netscape was still around. IE is much more forgiving.

You gotta detect which browser people are using and execute different code for each. Plenty of examples in the KB CSS code. Just download it and have a look.

[Big Dave]

Off topic, but did you know that one of the directors/important people for Futurama is David X. Cohen? It's true. Watch an episode (7:00pm C4)

Simpsons too - good old uncle X eh? It's one of the most common names there is. John Smith in Hebrew. (which I ain't)

[Matt Bleck]

Off topic again... The site looks good Dave. Just one bit of constructive critisism (however ya spell it). Some of your jpegs are over compressed giving a blochy look. If your using Photoshop to compress them try saving for the web and preview window will come up. you can change the settings to best suit each image.

apart from that looks clean and easy to use.

Oh and , Netscape SUCKS!!!

[Slingshot]

Does anyone actually use Netscape anymore? I'd say it'd be better to get it right for IE & Firefox.
For Netscape users (and IE users) just provide a download link to Firefox, it's so much better IMHO.

[skelstar]

I run an online rugby betting site (www.virtualrugby.net) which is reasonably heavy in CSS. I used FFox (Mac moslty and PC at work whoops) and found it far more forgiving than IE. Many a time windows/frames/tables/divs wouldnt size/align/colour/border properly in IE but would in FFox/Safari. Whenever any of my users complain I tell them its god punishing them for buying a faulty product (MS Windows 95 or greater).
Theres plenty of sites on the net that tell you the 'bugs'/nuances of the different browsers. I recommend googling 'Advanced CSS'.

Good luck.

[Big Dave]

Off topic again... The site looks good Dave. Just one bit of constructive critisism (however ya spell it). Some of your jpegs are over compressed giving a blochy look. If your using Photoshop to compress them try saving for the web and preview window will come up. you can change the settings to best suit each image.

apart from that looks clean and easy to use.

Oh and , Netscape SUCKS!!!

And control shift r lauches 'image ready'!
Thanks for that - I just noted mottley pixels (band name?) are more prominent on LCD screens too.
Have upped the ones on the top title frame to 9's.

[Matt Bleck]

And control shift r lauches 'image ready'!
Thanks for that - I just noted mottley pixels (band name?) are more prominent on LCD screens too.
Have upped the ones on the top title frame to 9's.


All good... thanks for the new shortcut!!!

[Big Dave]

All good... thanks for the new shortcut!!!

Doh! - that's command shift m - sorry.

[Matt Bleck]

Doh! - that's command shift m - sorry.
:rofl: No worries

[Groins_NZ]

So I spend most of last night getting my head around cascading style sheets. 'the way forward' people I respect tell me. Skinny code for nifty effects. The light side.

OK - I'll get away from the surplus nested tags and messy litter that dreamweaver can create and use a mix of html styles and css and go back to manually coding a lot of www.kiwirider.co.nz

All works fine except when i test it in netscape - no dice on the navigation effects.
Any of you guys have experience with this - i see there are a few different protocols for calling up the .css. Any that work with netscape that you know of?

Where do you start! I've done a few sights and designed them to work in both browsers but still, some things don't appear exactly the same - such as font sizes. Most differences between the two involved some kind of measurement value i.e. font size or table width/height. You can produce a satisfactory result in the end however - just takes a bit of time/experience and fiddling about.

Another option, like SpankMe suggested is to first detect what browser the user has and then load the appropriate stylesheet. You can find browser detection scripts all over the Web which usually revolve around a 'If, Then, Else' construct.

This example reference to an external stylesheet should work in any browser:

<LINK REL="stylesheet" HREF="/stylesheets/style.css" TYPE="text/css">

[Big Dave]

Writing CSS code that works in both IE and FF is a complete fucking pain. Found that out when do my personel page. (http://spankme.dynu.com/) Which is why I gave up on back when Netscape was still around. IE is much more forgiving.

You gotta detect which browser people are using and execute different code for each. Plenty of examples in the KB CSS code. Just download it and have a look.

thanks - what a pain. Looks like a few more hours. (:wait: or Ostrich it)

[Big Dave]

This example reference to an external stylesheet should work in any browser:

<LINK REL="stylesheet" HREF="/stylesheets/style.css" TYPE="text/css">


Ironically it doesn't work in mine. I'll copy the source and have a look.

[Skunk]

I always end up writing one stylesheet for the compliant browsers and another for IE and a third for Netscape - tho' these days I ignore Netscape... :motu:

I use PHP to detect the browser just in case javascript is turned off - that way its server side controlled.

And I've always used
<LINK REL="stylesheet" HREF="/stylesheets/style.css" TYPE="text/css"> to call the stylesheet (not as you have)

[Big Dave]

And I've always used <LINK REL="stylesheet" HREF="/stylesheets/style.css" TYPE="text/css"> to call the stylesheet (not as you have)


Makes more sense - and either one works fine in IE.
Implementing your link makes blockquotes dissapear in netscape 7.01. Which i'm now considering ignoring too...maybe, or maybe i just go back to html styles.

[Skunk]

...maybe, or maybe i just go back to html styles.
Don't.

Once you get CSS sorted in ya head it's much better - redesign the whole layout from the CSS etc. Don't have to touch the html at all.
Besides, I like to make people get a better browser (which is why I'm thinking of dropping support for the deranged IE.) pt