jQuery Forum

As of 1.3 $.browser is listed as deprecated in support of
jQuery.support.  The thinking is that developers should be basing their
checks on functionality instead of user agent strings.
I think this is throwing a lot of novice jQuery users as they see the
word deprecated and think that they shouldn't use it as the method is
going away.  From my understanding that method isn't going away. (<a href="http://osdir.com/ml/misc/2009-01/msg00001.html">http://osdir.com/ml/misc/2009-01/msg00001.html</a> "<i>According to John R, $.browser and version will remain in the core
indefinitely, despite being deprecated...</i>")  For
some cases it's really difficult to determine what piece of
functionality to use to get the desired result.  For instance, today, I
noticed a coworker used $.browser.safari to build code specific to a
Safari issue we were having.  Knowing that $.browser was listed as
deprecated I went to find the correct way to segment out safari using
$.support() unfortunately based on the docs I found this to be
impossible to easily determine which is the best approach to use and I
am still not sure it's possible.
I did some research to see if there was an easy way to segment Safari
from the rest using $.support() and found this thread on Stack Overflow
that seems to support developer confusion on the issue. 
<a href="http://stackoverflow.com/questions/584285/detecting-ie6-using-jquery-support">http://stackoverflow.com/questions/584285/detecting-ie6-using-jquery-support</a>
Developers want to do the right thing and listing the method as
deprecated flags the developer to avoid that method at all costs.  I
think it would be better to list the method as not a "best practice"
instead of deprecated and explain why functionality checks are better
then user agent sniffing.
Also it would be good to flush out some scenarios for developers to use
which functionality test for certain browsers and certain scenarios.
Thoughts? Am I off base on this?
Ralph

http://dev.jquery.com/ticket/4148
Is a duplicate and can be closed, user hit submit and didn't preview
first then recreated the ticket in 4149 with proper formatting.
http://dev.jquery.com/ticket/4149
I don't think this is a problem with jQuery. Submitter is injecting
jquery onto a page and I think the .replace method is overriding in a
way that is unintended from the original page authors intent.

I've found that I enjoy looking at bugs and trying to replicate them
and adding detail to the ticket to help the actual bug fixer with the
issue when they can get around to fixing it.
Take for example this ticket: http://dev.jquery.com/ticket/4081
I was able to recreate the bug and added some more details of my
testing. First question, is this beneficial to the bug fixers? Am I
wasting my time?
A couple of tickets I found aren't really bugs at all and could
probably be closed:
Take this one for example: http://dev.jquery.com/ticket/4091
I was able to explain to the bug reporter that the problem laid with
his syntax, the ticket probably could be reviewed first before being
closed but I feel the leg work was done on my part and this ticket
could be handed off to someone who could quickly ascertain if it can
be closed or needs more help.
And finally I came across an example where the reporter was using a
faulty tool and the ticket had no merit.
This example: http://dev.jquery.com/ticket/3919
I feel that I could safely close this ticket and help ease the burden
of that issue later for someone. Which brings me to my real
question.
What is the process for gaining permission to work with the meta data
of a ticket and close a ticket? What do I need to work on to get to
that point? Should I continue the work that I am doing currently?
Thanks,
Ralph Whitbeck

I wrote a blog post awhile ago on how to pull in Twitters API via JSON
and consume it with jQuery.
http://damnralph.com/2007/11/20/PullingTwitterUpdatesWithJSONAndJQuer...
As you can see in the comments some people are having problems with
the code I posted. The problem seems to be when you reload the page.
jQuery seems to add a second callback method thus making the JSON data
from twitter invalid and breaking the javascript on the page.
Here is a page that only has the example code:
http://www.damnralph.com/content/binary/twitter-json-jquery.html
Can someone look at this and tell me 1. am I doing something wrong? 2.
Is this a bug with getJSON and should I post a bug report? 3. Is this
just a bug with the Twitter API and should I post a bug report?
Thanks
Ralph Whitbeck

I wrote a blog post awhile ago on how to pull in Twitters API via JSON
and consume it with jQuery.
http://damnralph.com/2007/11/20/PullingTwitterUpdatesWithJSONAndJQuery.aspx
As you can see in the comments some people are having problems with
the code I posted. The problem seems to be when you reload the page.
jQuery seems to add a second callback method thus making the JSON data
from twitter invalid and breaking the javascript on the page.
Here is a page that only has the example code:
http://www.damnralph.com/content/binary/twitter-json-jquery.html
Can someone look at this and tell me 1. am I doing something wrong? 2.
Is this a bug with getJSON and should I post a bug report? 3. Is this
just a bug with the Twitter API and should I post a bug report?
Thanks