Superfish could be the standard for Drupal themes instead of everyone independently implementing suckerfish. Please move it into core.

I created a superfish module to add superfish to old themes and and replace suckerfish in new themes. See discussion: http://drupal.org/node/354974

As an add on module, few themes will move because you cannot rely on add on modules. If superfish moved into the core theme code and automatically added a superfish option to theme settings, everyone could use it.

Comments

peterx’s picture

I tested Superfish with a dozen themes at 02d.in. All integrated ok. Some need CSS styling altered slightly. Changing the default height would work. There were only slight variations of the div id and class needed, by default, to connect Superfish to menus without altering Superfish. You can test the result by registering and selecting the various themes in your account.

bwv’s picture

Thanks to roopletheme, I am using it at the top of my record store site (classicvinyl.biz) in a custom region I created. Works nicely.

peterx’s picture

classicvinyl.biz loaded slowly and produced:
Connection failure: Read timed out: <script type="text/javascript" src="/misc/drupal.js">

If you find a solution that requires a change to Superfish, please feed the change back to Superfish. The ideal is to use a well maintained Superfish library instead of building a special Drupal version, the same as we do with jQuery.

bwv’s picture

Thanks, I noticed that in IE 5.5 and IE 6.0 there were problems with page load time. Not so with FF and Google Chrome, however. I have disabled the Superfish menu for now until I can find a solution. What browser were you using when you visited the site? Anyone else having trouble with the load time?

mdupont’s picture

Version: 6.x-dev » 8.x-dev

Features go against latest dev version. IMO I don't see Superfish used that often so I don't think it should be in core.

Everett Zufelt’s picture

Status: Active » Closed (won't fix)

Superfish menus are incredibly difficult to make work properly for accessibility, e.g. I have never run across a superfish that actually is easy to use for all users (primarily keyboard / screen-reader).

Marking won't fix as old issue, and IMO not a good idea for Core.