So I decided to side step my go to dropdown menu script and give the CSS approach a shot. As I’m sure you have deducted based off the title of this entry I decided to go with the Suckerfish approach. What resulted I believe is somewhat noteworthy inconsideration of some very complex and non-standard approaches I have worked with in the past. However, I think it’s important to keep in mind a few things when dealing with this approach.

1. The Suckerfish technique requires very confusing as well as bloated CSS to produce the required effect. Skinning the menu and creating the desired functionality specific to the design is exhaustive. I did however improve upon my CSS knowledge. Truth be told I’m not really convinced it’s a better route than going with an off the shelf menu that can be implemented quickly.
2. The menu system seemly conflicts with any element on the same page that has a CSS overflow property set to auto. It will cause a flicker on the page in Firefox when the menu system is rolled-over. I have yet to find a work around.
3. I think one of the creators of the suckerfish method is correct in saying, “It has been a popular method of applying dropdown menus thanks to its lightweight, standards-compliant, accessible, cross-browser nature�. True, but in my opinion it’s not a good choice for a complex menu requiring flexible functionality and liberal interface design.