CSS Menus

WGAFA

Member
Joined
Sep 21, 2009
Messages
14
Reaction score
4
Location
Cape Town
Hi all for those html raw coders, found an awesome site to let you create menus CSS easily. Having searched and tried suckerfish and son of sucker fish, and a few other sites this one is awesome, check it out http://purecssmenu.com

Once created, you download and paste into your style sheet page or whereever
 
That's quite a nice menu there. Also consider http://jquery.com/ . It's a complete JavaScript library with much more than just menu's. It's a bit tricky at first, since the syntax tends to be a bit different from everyday JavaScript, but they have some pretty nifty features. Sites like Digg, Facebook, del.icio.us, etc also make use of this library.
 
That's quite a nice menu there. Also consider http://jquery.com/ . It's a complete JavaScript library with much more than just menu's. It's a bit tricky at first, since the syntax tends to be a bit different from everyday JavaScript, but they have some pretty nifty features. Sites like Digg, Facebook, del.icio.us, etc also make use of this library.

The benefit of using CSS for menus is that client browsers with Javascript disabled will still be able to access the menu. If JS is disabled or not supported on the client side, then jQuery will fail. ;)
 
The benefit of using CSS for menus is that client browsers with Javascript disabled will still be able to access the menu. If JS is disabled or not supported on the client side, then jQuery will fail. ;)

not to mention that jq isn't even in final release yet, its still alpha and might brake along the line when real standards change.
 
not to mention that jq isn't even in final release yet, its still alpha and might brake along the line when real standards change.

Yeah well, I was actually referring to JS in general. If JS is disabled on client side, it won't matter if you use an open source JS library or your own proprietary code - it won't work. :)
 
Yeah well, I was actually referring to JS in general. If JS is disabled on client side, it won't matter if you use an open source JS library or your own proprietary code - it won't work. :)

that too :D, imho it is always best to implement as little as js/jq as possible...
 
Last edited:
that too :D, imho it is always best to implement as little as js/jq as possible...

I think it depends on the application and audience. If you build software that you sell off to multiple clients, you can make JS a requirement. If you're just building a site intended to reach people across the globe (or even some astronauts? :p), you'll have to be careful to implement client-side scripting...
 
CSS Menu rendering

I am not sure how the different browsers render CSS, but I would suspect there is some jscript involved.

What I like about CSS Menu link I posted, over about the other ones found is that it produces code that was relatively easy to customize to you unique requirement. I have I tested it with .net (with the obvious mods) and it seems to work well
 
CSS is not dependent on any client-side scripting, so it should work quite well, based on the browser's implementation of the CSS standards. Typical CSS menus (like those in the link) should work well in all popular modern browsers (Firefox 2+, IE7+, Chrome, Opera 8+, Safari 2+), but older browsers (like IE6 :sick:) will give you tons of trouble with many CSS-based menus. For those instances its wise to use Javascript. Best implementation therefore would be CSS for all modern browsers and an "override" for IE6.
 
Sorry to wake a mummy :p
but older browsers (like IE6 :sick:) will give you tons of trouble with many CSS-based menus. For those instances its wise to use Javascript. Best implementation therefore would be CSS for all modern browsers and an "override" for IE6.
CSS menus are cool, but when you have users on IE6 and can't tell them that they have to upgrade because they are working at one of the bigger financial institutions, your options are numbered. :cry:
 
I'd rather tell the big institution to waketf up and get with the times, or move on.
 
I'd rather tell the big institution to waketf up and get with the times, or move on.
Old Mutual can't even install XP SP3, so whats the chance of them installing IE7/8??

By the way, XP SP2 is not a supported OS anymore so they will have to upgrade anyways.
 
I think this has been mentioned in various threads here before, but the main reason many corporates refuse to upgrade, is because the risk there is in existing systems (like financial / project management / ERP / intranets) failing to work correctly on modern browsers. Many legacy web apps were designed with their specific target market in mind - XP users running IE6. Since these corporates paid gazillions or Rands to get these systems up and running, they're trying to protect their investment.

Just my 2c, from experience...
 
Sorry to wake a mummy :pCSS menus are cool, but when you have users on IE6 and can't tell them that they have to upgrade because they are working at one of the bigger financial institutions, your options are numbered. :cry:

Use a script like ie7.js (or the later ie8.js - Google for it) - then you can go ahead with most of what you'd otherwise miss. Use conditional CSS too, to reach your widest possible audience.
 
Top
Sign up to the MyBroadband newsletter
X