Really like this module, yet I always have to add css like
.sf-menu li { background: transparent !important; border: 0 solid none;}
or similar. Would absolutely love to have a neutral style that doesn't add a background colors or borders. Better yet it would be great to make the default this way. If you will consider a patch, I am willing to patch the default style to do this.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | superstyles.patch | 10.85 KB | akalata |
| #7 | default.css_.txt | 718 bytes | akalata |
| #4 | clean.css_.txt | 1.05 KB | lucascaro |
Comments
Comment #1
mehrpadin commentedHey Geoff,
In fact, the idea was to keep all the SF stuffs untouched, therefore having very little problem when upgrading to any new version of the jQuery SF plugin; however I already changed some CSS stuffs, so maybe we should think of this too.
Comment #2
lucascaro commentedsubscribing. a neutral style would make things much easier :)
Comment #3
danny_joris commented+1
Comment #4
lucascaro commentedhere is the neutral css:
Comment #5
mellenger commentedperfect, thanks!
Comment #6
dvasquez commentedWhy the menu is not displayed in IE when I set opacity styles?
filter: alpha(opacity=80);
Can you help me?
Comment #7
akalata commentedHere's a patch against 6.x-1.6, incorporating mshepherd's additional css from #776480: Additonal styles and a non-styled "None" (since "neutral" could imply a color scheme), moving all of the old defaults to a new file.
I toyed with having None be the default, but decided that wouldn't be fair to anyone not strong in CSS/theming. However, I turned the shadow default "off," to be one less step for people who want to use None as a compromise; feel free to switch that back if you want.
Also wanted to name it Naked, but was worried that people might freak out when "naked" appeared in the CSS.
A few of my own errors I couldn't get past:
- I was able to add mshepherd's new css files by cutting/pasting his patch nearly exactly, but I couldn't figure out how to include my new file, the default.css. If anyone wants to test without fixing my patch, I've attached the default.css file which goes in css/extras.
- I also get an "unexpected end of file in patch" error when I apply the patch, but everything works as expected.
@dvasquez - please open up a new issue with your support request as it is unrelated to the rest of the discussion in this thread.
Comment #8
lucascaro commentedHi there, I think the patch didn't apply correctly. Here is what I've got:
patching file ./css/superfish.css
patching file ./superfish.module
patching file ../superfish-1/css/extra/vision-blue.css
patching file ../superfish-1/css/extra/vision-green.css
patching file ../superfish-1/css/extra/vision-purple.css
patching file ../superfish-1/css/extra/vision-red.css
patching file ../superfish-1/css/extra/vision-yellow.css
patching file ../superfish-1/css/extra/default.css
patch: **** malformed patch at line 335:
Is this correct? Some files are being created in the superfish-1 directory. is this the backup?
Comment #9
akalata commented@lucascaro no, that's just me not knowing how to create a patch :)
Comment #10
pawel.traczynski commentedHi!
There should be also an option to disable the JavaScript at all. This module would be a good one if the menu worked without the JS too. Have a look at nice_menus module - if you disable JavaScript it still works just without animation. And the Superfish doesn't which makes it unprofessional. Actually the only thing which this module has better than nice_menus is an option to add tags into menu code to allow the creation of sliding-door menu buttons. The nice_menus module now also has superfish included but it was much better without it.
Och, and I'm not complainig by the way - just wanted to point some things out :-)
Best,
Paul
Comment #11
mehrpadin commentedHey Pawel,
May I see an example?
Comment #12
mehrpadin commentedFor the record: requested feature added as of version 1.8 :)