I thought this as well, $.browser still works, as many plugins use it,
but I'm interested in what we should be using.
fambi wrote:
Having just upgraded to 1.3.2, I've realised that the $.browser
utility has been deprecated.
Does this mean it is no longer possible to identify which browser
http://docs.jquery.com/Utilities/jQuery.support
jQuery now uses feature detection. There are some good links to
explain in the post above. It is still possible to detect which
browser is being used (plain old js) but jQuery support will probably
be removed at some point in the future.
On Wed,
ok, lets say I wanted to target IE6 only, how would I do that with support?
Aaron Gundel wrote:
http://docs.jquery.com/Utilities/jQuery.support
jQuery now uses feature detection. There are some good links to
explain in the post above. It is still possible to detect which
browser is being
You would need to find whatever quirk it is you are targeting and
create a function or otherwise create a scenario where that quirk is
exposed, and use that to populate some identifier.
eg: jQuery detects support.opacity by creating a div
style=opacity:0.5 and then later testing the opacity
Its better to detect features not browsers; that said detecting a single
browser such as ie6 I would use conditional comments feeling assured that
the code is not interfering with other bits
http://www.sitepoint.com/forums/showthread.php?t=455334
2009/2/25 Liam Potter radioactiv...@gmail.com
On Wed, Feb 25, 2009 at 11:19 AM, Sam Sherlock sam.sherl...@gmail.com wrote:
Its better to detect features not browsers; that said detecting a single
browser such as ie6 I would use conditional comments feeling assured that
the code is not interfering with other bits
Then we probably need a plugin for this.
Because browser detection can also be used for information (not only
development).
According to John Resig $.browser will remain for the foreseeable
future. Being deprecated doesn't mean it will be removed soon (or at
all). If you're targeting IE6 quirks I'd think it's not that bad to
keep using browser detection, but if you're using it to differentiate
modern browsers it's
On Feb 25, 11:59 am, brian bally.z...@gmail.com wrote:
Conditional Comments are great and all (best thing to come from MS
since asynchronous requests) but they're not the best solution here,
IMHO. Whether it's the browser or a feature that needs detecting, it's
often required somewhere in the
On Wed, Feb 25, 2009 at 2:26 PM, Matt Kruse m...@thekrusefamily.com wrote:
On Feb 25, 11:59 am, brian bally.z...@gmail.com wrote:
Conditional Comments are great and all (best thing to come from MS
since asynchronous requests) but they're not the best solution here,
IMHO. Whether it's the
10 matches
Mail list logo
