![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Yes, all JS will stop working. Search engines do not execute JS anyway. I put that in that way to ease the burden of changing it annually. I've no doubt there's a better way, but that seemed to work and I stopped looking. Quest will resume. Look into SSI or PHP includes. F1 has good information about it. Tell me it isn't so! Do we really have to learn SSI or PHP to make our web sites work right? |
|
Where's the straight jacket? I'm turning myself into the local Funny Farm. |

#12
| ||||
| ||||
|
|
Wait! Don't go there until you've developed a complete list of buzz words for the bingo game. PHP, ASP, ColdFusion, Perl, CGI, |

|
Yes, all JS will stop working. Search engines do not execute JS anyway. |
|
But for using a single file for inlcusion in multiple pages, it is more reliable than JavaScript. And very handy! |
|
There really isn't much to learn for SSI, but your server does need to support it. If you go the PHP route, chances are, you might decide to use |
#13
| |||
| |||
|
|
I got a kick out of your response. I think I should make that song my alma mater. :-) |

|
Yes, all JS will stop working. Search engines do not execute JS anyway. What about Project Seven Menus? Aren't they based on JS? |

#14
| |||
| |||
|
|
To cover a situation where JS may be off or unavailable, always have the main menu item link to a page which contains links to sub pages that are/were |
|
Use JS to enhance a site, but do not depend on it or require it to provide information from the site. |
#15
| |||
| |||
|
|
A common mistake I've seen people make when using a JS-based menu is neglecting to include a link in a top level menu item when there are submenus. To cover a situation where JS may be off or unavailable, always have the main menu item link to a page which contains links to sub pages that are/were included in the submenu - and some relavent content, of course. |
|
Use JS to enhance a site, but do not depend on it or require it to provide information from the site. |
#16
| |||
| |||
|
|
To cover a situation where JS may be off or unavailable, always have the main menu item link to a page which contains links to sub pages that are/were included in the submenu - and some relavent content, of course. Use JS to enhance a site, but do not depend on it or require it to provide information from the site. Good to know. One of my own websites has information contained within an accordion panel. I was thinking of upgrading to the new Accordion Panel Magic 2. Any thoughts on that? |
#17
| |||
| |||
|
|
Good to know. One of my own websites has information contained within an accordion panel. I was thinking of upgrading to the new Accordion Panel Magic 2. Any thoughts on that? |

#18
| |||
| |||
|
|
"Mark A. Boyd" <lingoboyd (AT) mboydDotcom (DOT) invalid> wrote in message news:Xns9BDB6E989FA90mblistssanDotrrcom (AT) 216 (DOT) 104.212.96... A common mistake I've seen people make when using a JS-based menu is neglecting to include a link in a top level menu item when there are submenus. Great point, Mark. We actually built in a failsafe for just that in PMM2 so that if folks leave the root item as a null link, we grab the first link in the submenu and assign it to the root. For times when script is disabled, our approach is from a more measured accessibility perspective than most others. For a large menu, simply revealing it is often the worst thing you can do for blind people and for people who must use a keyboard. Our user guide discusses these topics and points to a live demo: http://www.projectseven.com/products/menusystems/pmm2/ug-examples/a ccessible/ |

#19
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |