![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm looking for a template or model for menus that drop down when the mouse hovers over them. Criteria: must work without JS, even in IE, must degrade acceptably in non-CSS browsers, must not be sized in pixels. |
#3
| |||
| |||
|
|
Stan Brown wrote: I'm looking for a template or model for menus that drop down when the mouse hovers over them. Criteria: must work without JS, even in IE, must degrade acceptably in non-CSS browsers, must not be sized in pixels. You might want to look at the Brothercake menu http://www.brothercake.com/dropdown/ |
#4
| |||
| |||
|
|
Stan Brown meinte: must work without JS, even in IE, I suppose that's pretty impossible. If you're talking about IE6 or earlier. Anyway, "dropdown menus for ie without javascript" gives me 106.000 hits. Still, I don't think there is a pure-css-and-ie6-too version among them. |
#5
| |||
| |||
|
|
Here's one: http://barefile.com.au/cssmenu/ Even supports IE5.5. |
#6
| |||
| |||
|
|
"Gregor Kofler" <usenet (AT) gregorkofler (DOT) at> wrote in message news:7a3ee$4785667d$557fb479$17585 (AT) news (DOT) inode.at... Stan Brown meinte: must work without JS, even in IE, I suppose that's pretty impossible. If you're talking about IE6 or earlier. Anyway, "dropdown menus for ie without javascript" gives me 106.000 hits. Still, I don't think there is a pure-css-and-ie6-too version among them. Here's one: http://barefile.com.au/cssmenu/ Even supports IE5.5. |
#7
| |||
| |||
|
|
rf wrote: "Gregor Kofler" <usenet (AT) gregorkofler (DOT) at> wrote in message news:7a3ee$4785667d$557fb479$17585 (AT) news (DOT) inode.at... Stan Brown meinte: must work without JS, even in IE, I suppose that's pretty impossible. If you're talking about IE6 or earlier. Anyway, "dropdown menus for ie without javascript" gives me 106.000 hits. Still, I don't think there is a pure-css-and-ie6-too version among them. Here's one: http://barefile.com.au/cssmenu/ Even supports IE5.5. Richard, that looks very interesting! Do you have anything written up that explains the techniques you used? |
|
Specifically, examining the HTML/CSS I'm wondering about the structure of the second and third menu items from the left. |
#8
| |||
| |||
|
|
"Ed Mullen" <ed (AT) edmullen (DOT) net> wrote in message news:hM6dnYFHftqx8hfanZ2dnUVZ_vmlnZ2d (AT) comcast (DOT) com... rf wrote: "Gregor Kofler" <usenet (AT) gregorkofler (DOT) at> wrote in message news:7a3ee$4785667d$557fb479$17585 (AT) news (DOT) inode.at... Stan Brown meinte: must work without JS, even in IE, I suppose that's pretty impossible. If you're talking about IE6 or earlier. Anyway, "dropdown menus for ie without javascript" gives me 106.000 hits. Still, I don't think there is a pure-css-and-ie6-too version among them. Here's one: http://barefile.com.au/cssmenu/ Even supports IE5.5. Richard, that looks very interesting! Do you have anything written up that explains the techniques you used? Not as yet. I just pulled it out of one of my CMS's in answer to a post a few weeks ago. Specifically, examining the HTML/CSS I'm wondering about the structure of the second and third menu items from the left. Nothing very dramatic. The sub-menu is in a table, initially hidden and positioned absolutely in its (relatively positioned) parent. The conditional comments determine what HTML each browser sees. Specifically: !--[if gt IE 6]><!--></a><!--<![endif]-- The </a> will be seen by IE7 (and above) because of the conditional comments, and all non-IE browsers who correctly parse away the comments. This method is explained on Microsofts site, it's kind of a reverse conditional comment. !--[if lte IE 6]></a><![endif]-- The </a> is only seen by IE 6 and below. As for the menu: IE6 and below see a <li> (the top level item) containing a <a> _which contains the table_. Visibility of the table is controlled by .nav a:hover table. This is of course invalid HTML but who cares, we are throwing it only at IE6 and below and they seem quite happy with it. All other browsers see a <li> containing both a <a> and the table, with the table _following_ the <a>. Visibility of the table is controlled by .nav li:hover table. Note there is a bit of fluff in the HTML to allow the CMS to apply differing effects to the menu. |
#9
| |||
| |||
|
|
"Ed Mullen" <ed (AT) edmullen (DOT) net> wrote in message news:hM6dnYFHftqx8hfanZ2dnUVZ_vmlnZ2d (AT) comcast (DOT) com... rf wrote: "Gregor Kofler" <usenet (AT) gregorkofler (DOT) at> wrote in message news:7a3ee$4785667d$557fb479$17585 (AT) news (DOT) inode.at... Stan Brown meinte: must work without JS, even in IE, I suppose that's pretty impossible. If you're talking about IE6 or earlier. Anyway, "dropdown menus for ie without javascript" gives me 106.000 hits. Still, I don't think there is a pure-css-and-ie6-too version among them. Here's one: http://barefile.com.au/cssmenu/ Even supports IE5.5. Richard, that looks very interesting! Do you have anything written up that explains the techniques you used? Not as yet. I just pulled it out of one of my CMS's in answer to a post a few weeks ago. Specifically, examining the HTML/CSS I'm wondering about the structure of the second and third menu items from the left. Nothing very dramatic. The sub-menu is in a table, initially hidden and positioned absolutely in its (relatively positioned) parent. The conditional comments determine what HTML each browser sees. Specifically: !--[if gt IE 6]><!--></a><!--<![endif]-- The </a> will be seen by IE7 (and above) because of the conditional comments, and all non-IE browsers who correctly parse away the comments. This method is explained on Microsofts site, it's kind of a reverse conditional comment. !--[if lte IE 6]></a><![endif]-- The </a> is only seen by IE 6 and below. As for the menu: IE6 and below see a <li> (the top level item) containing a <a> _which contains the table_. Visibility of the table is controlled by .nav a:hover table. This is of course invalid HTML but who cares, we are throwing it only at IE6 and below and they seem quite happy with it. All other browsers see a <li> containing both a <a> and the table, with the table _following_ the <a>. Visibility of the table is controlled by .nav li:hover table. Note there is a bit of fluff in the HTML to allow the CMS to apply differing effects to the menu. |
#10
| |||
| |||
|
|
rf wrote: "Ed Mullen" <ed (AT) edmullen (DOT) net> wrote in message news:hM6dnYFHftqx8hfanZ2dnUVZ_vmlnZ2d (AT) comcast (DOT) com... rf wrote: http://barefile.com.au/cssmenu/ Thanks again for this, Richard. Ok, I've been spending some time on it and I have a couple of questions. 1. Why use a table for the menu items? As opposed to list items, for example? |
|
2. Do you have an example of this scheme which implements additional sub-levels? |
|
Why do we drive on parkways and park on driveways? |
![]() |
| Thread Tools | |
| Display Modes | |
| |