it'd probably help if i included the link ;) http://www.quirksmode.org/js/detect.html
On Sep 5, 1:15 pm, "ryan.j" <ryan.joyce...@googlemail.com> wrote: > It would appear this is the inevitable result of us all using feature > detection rather than browser sniffing - essentially we're still doing > all the same stuff as before, but in a more roundabout way because we > need to test for features specific to a browser but - and this is the > important bit - not necessarily related to the issue we're trying to > circumvent. > > if all else fails, have a peek at BrowserDetect.browser > > On Sep 4, 5:56 pm, D A <dali...@gmail.com> wrote: > > > Now that we're switching to feature detection rather than browser > > detection, how does/should one detect for a webkit browser? > > > Is there a known feature that we can check for that would Identify > > Safari and Chrome? > > > We're running into some (rather minor) layout issues with some jquery > > plug-in rendered content in Chrome and Safari and it'd be really easy > > to just do a 'if a webkit browser, tweak this' type of logic. > > > -Darrel
