> From: ".jeff" <jeff at members.evolt.org> > > actually it does account for js-disabled browsers. if you don't have > js enabled you won't see the expand/collapse all link or > expand/collapse comment links. it would also account for > mis-detection or the likelihood that we remove the serverside > detection and fail gracefully for those users that don't support the > w3c dom method of object finding (getElementById). very cool... it's hidden, i assume, and made visible by JS? it would still appear for those poor NN3 users, though, if you eliminate server-side detection, correct? or no? > :~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > : it is my belief that the code should come off the > : server the same for everyone, built to support the > : lowest baseline, and have features added to support > : the higher-end, without detracting from the usability > : of the lower-ends of the scale... > :~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > for the sake of argument i've removed the serverside detection. what > about the way it's done does not achieve what you've outlined above? > i'm not asking in an effort to keep this particular feature. i'd just > like to know for the future. it's handled as well as it can be handled, i have no issue with the coding prowess involved here... i'm just taking a more purist approach... we claimed one template for all users, so why not stick to it? it's really more about our credibility than anything else... > :~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > : > your problem must exist with us detecting and > : > placing enhancements based on browser rather > : > than feature detection, right? i'm sure that > : > can be implemented. > : > : exactly... > :~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > you can't do feature detection on the server, unfortunately. so, i > removed the serverside browser detection and am sending it down the > pipe to everyone. if they have js enabled *and* support the > getElementById() method i set up the page for them. if either of > those are not true, then they don't see all the expand/collapse links. i know you can't do JS feature detection on the server... and i don't have time right now to track down the URL and fire up NN3, so i trust your implementation... you'll not i'm no longer very concerned with the code itself, but with the overall approach and message associated with it... is it silly of me? dunno... > :~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > : > the inclusion of a richtext editor for IE5+ or > : > ie5/nn6+ or whatever, or even based on the > : > features required for it to work, does not > : > reduce functionality of the site at all. > : > : no, the inclusion doesn't... but if it's inclusion > : followed by lack of support in any way slows a user, > : then it might not be a good idea... the 'feature' > : isn't a bad thing, it's just an issue of how it's > : implemented... > :~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > agreed. rock. are you gonna eat that?