> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark > J. Reed > Sent: Monday, December 11, 2006 8:57 PM > To: Andy Pemberton > Cc: Russ Peters; css-d@lists.css-discuss.org > Subject: Re: [css-d] Div show/hide > > Seen the rant. I agree that links to content should be, at their > core, plain links that would, absent JavaScript, take you to a new > page with the content, said behavior then available to be modified by > JavaScript to do something else, preferably without making the core > behavior inaccessible even in JavaScript-enabled contexts. If I were > writing the page, I would go further along the principles of > non-intrusive JavaScript and not use the "onclick" attribute in HTML, > either, but instead assign the link an ID and then have initialization > code in an external script file set its onclick property. > [snip]
Thank you all for responding..yes, now it's obvious this is more of a JavaScript question versus a CSS question. I was focused on the display:none/display:block functionality and not the real problem which was the javascript. It's a great point that for usability I need to give the user access to that information if they have scripting disabled. I'm going to try and either incorporate a link into the url with the onClick attribute or modify the script. If helpful I'll post my shot at fixing this unless this should move over to the javascript list. Russ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
