That's fine and all but the issue is how does one 'detect' those browsers that are incompatible with jQuery without sniffing? The answer is, you don't. I've scoured every inch of the web looking for that answer; from object detection to feature detection. Browser sniffing seems to be the only solution in this case. Personally, I would suggest the writing of a library that would detect those objects used within jQuery. The list would most likely be massive (a series of successive conditional statements). We're talking about an "if browser is jQuery compatible" function that would obviously work outside of the jQuery environment in order to make that determination. The task sounds rather daunting actually and that's why sniffing might be the only way to go.
On Feb 1, 2:07 pm, Klaus Hartl <klaus.ha...@googlemail.com> wrote: > It's as simple as that: in the first step build a page completely > without JavaScript so that everything works fine. Then add JavaScript/ > jQuery to the game and improve the user experience.This concept is > also referred to as Progressive Enhancement. You will find quite some > information about it on the web. > > --Klaus > > On 1 Feb., 16:31, WebWiz <web...@gmail.com> wrote: > > > I'm new to jQuery so I apologize if this is a dumb question. I'd like > > to take advantage of the visually interesting things jQuery can do. > > But I'm bumping into a small but significant number of end users who > > either have JavaScript disabled or are running old browsers with bad > > JS support. Since I want to provide at least a decent experience for > > all site visitors, I'm wondering if there are any guidelines, > > suggestions, or tips on how to build a web page so whatever's being > > done via jQuery still works and looks OK if JavaScript isn't coming > > along for the ride. > > > Thanks!
