On Tue, 03 Aug 2010 11:29:15 +0100, Bobby Jack <[email protected]> wrote:
> Of course, that method doesn't help if you don't have CSS enabled or if, > for example, you're using a screen reader. You could also use javascript > to remove the 'href' attribute, but that suffers from the same sort of > problem. > > Ideally, you'd remove the href element server-side so the *content* is > accurate. There shouldn't be any case where this is difficult. Yes, if > you're just including a single static chunk of HTML for your menu, this > isn't possible, so it's better to either dynamically generate the menu, > or have a separate static 'chunk' for each different state. If your menu > has more than one level of navigation, you'll need to do this anyway. > > - Bobby Agreed, without CSS it does not work and similarly doesn't take into account screen readers, however it seems much more probable that a 'normal' browser will have CSS enabled whereas JavaScript can more easily be disabled in many situations. The method works for relatively simple sites and handles SSI/PHP Includes, but it can soon become tiresome to write large sets of matching attributes to catch the correct pages. It will work with multi-level menus, but again can become complex on any but smallish sites. It is an easy and quite stable method for anyone who does not have the skills, or the need to start writing the dynamic scripts. The usual caveat applies that not all browsers respect the 'pointer-events' as yet. Best wishes Duncan -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
