Isn't that just a quick regex away from making it work with the new syntax?
-- dz
On Fri, Oct 2, 2009 at 10:26 AM, Matt Kruse wrote:
>
> My example code uses this selector syntax: t...@class^=child-]
>
> Support for [...@attribute...] has been changed to just [attribute...]
> with jQuery 1.3.
He's using the unit testing framework, so that part isn't needed
-- dz
On Tue, Sep 22, 2009 at 3:38 PM, DBJDBJ wrote:
>
> It is blatantly obvious and therefore difficult to spot ...
> I think your test page does things without
>
> $( function () {
> ...
> }) ;
>
> It that matters ?
> >
>
--~
On Sep 2, 2009, at 9:33 PM, DBJDBJ wrote:
> @dz: At last a number for you ;o) Andrea says that IE versions of jQ
> are 10 times slower ...
We already knew that -- jQuery in IE is slower because:
1. The workarounds are slower.
2. IE6/7/8's js engines are slower.
The slowness of jQuery -- or rea
On Sep 2, 2009, at 4:39 AM, DBJDBJ wrote:
> I do not need any kind of tests to be convinced that
> having different jQ for IE and other browsers is a good thing. And
> that it must bring measurable benefits, in terms of speed and
> stability, of future jQuery releases (if adopted).
It's called C
On Sep 2, 2009, at 5:43 AM, Andrea Giammarchi wrote:
> I think the best approach is to understand runtime what the browser
> can do and what it cannot then call right pieces of the puzzle in
> order to create the "perfect library".
>
> This will mean a sort of nightmare for each created ticke
The easiest way is to just use a class or id on the body:
js:
$('body').removeClass('theme_1').addClass('theme_2');
-- dz
On Tue, Sep 1, 2009 at 11:08 AM, Badbeer wrote:
>
> If it were me, I'd do it differently. For example:
>
> In my page, I would have a list representing all the sheets
On Tue, Sep 1, 2009 at 11:45 AM, DBJDBJ wrote:
>
> @dz No offence, but why are you taking part in this "pointless
> discussion" ?
Because if there *is* a significant speed increase, it's valid and
therefore interesting. There's a lot of sound and fury, but not a lot
of data.
> I am really puzz
Then run some tests! Take your no brainers, apply them to a recent
checkout of jQuery, and record some data!
You said that separating out IE stuff from jQuery into a separate
branch would show "measurable benefits (in spead increase and
stability)."
I'll repeat, because you seem to have missed t
On Mon, Aug 31, 2009 at 3:08 AM, DBJDBJ wrote:
> My intent
>
> Develop simpler, faster and more stable jQuery. This kind of delivery,
> would show measurable benefits (in spead increase and stability). It's
> a "no brainer": Imagine jQuery with zero IE workarounds inside.
I've yet to see any sign
Couldn't you do:
if(!!$(ele).attr('disabled')) {
//stuff
}
-- dz
On Thu, Aug 27, 2009 at 1:15 PM, William Chang wrote:
>
> Hey Matt,
> I understand now. Thanks!
>
> So, how do you avoid using attr() when you need to check for an
> attribute in the element? And, getting the value from an
Exactly. Also, two things:
1. Can we stop with the silly M$ nomenclature? We're not script
kiddies with an axe to grind.
2. Again, building an advanced web application does not mean
forgetting the lessons of progressive enhancement. Using advanced
features of newer browsers does not preclude p
ficant roadblocks to the
further development of jQuery core, I don't see what benefit anyone
gains from removing that support.
-- dz
On Wed, Jul 22, 2009 at 4:51 AM, David Zhou wrote:
>> jQuery and IE old : I am wondering why mainstream jQ supports IE6
>> actually? How many devel
> jQuery and IE old : I am wondering why mainstream jQ supports IE6
> actually? How many developers actually need and use that? Who and when
> will be developing an web app today , that will run on IE6 too ? 99%
> of web apps developed on jQ are new apps for new browsers.
That's a pretty myopic
On Mon, Jul 20, 2009 at 2:46 AM, DBJDBJ wrote:
>
> Well the only reason this is a link to a blog is the image present.
> Which speaks a thousand words. Which in turn should make the
> discussion here productive.
> Same as any other useful discussion on this good forum about legacy
> browsers issue
jquery-dev is not your personal soapbox. If you're going to
shamelessly plug your blog, can you at least plug a post that's
reasonably related to jquery development?
/rant
-- dz
On Sun, Jul 19, 2009 at 1:13 PM, DBJDBJ wrote:
>
> http://dbj.org/dbj/?p=244
>
> --DBJ
> >
>
--~--~-~--~-
Checkout the jQuery svn repo, make your changes and generate a diff.
-- dz
On Tue, Jun 16, 2009 at 11:34 PM, vdhant wrote:
>
> Hey guys
> In the meantime how could I go about creating my own patch that fixes
> this issue???
> Cheers
> Anthony
>
> On Jun 17, 1:11 pm, Daniel Friesen wrote:
> >
Just do a document.write() and bypass jQuery.
if (thehour >= 18)
document.write(...);
Since you're just checking time, you don't need to wait for the DOM to be
ready or any of that sort of thing.
-- dz
On Thu, Jun 4, 2009 at 12:23 PM, jez wrote:
>
> Hello,
> I am almost certain one of you
blem, I mean
> errors check )
>
> On Tue, May 19, 2009 at 3:23 PM, Matt Kruse wrote:
>>
>> On May 19, 7:51 am, David Zhou wrote:
>> > I wonder if it's feasible to monkeypatch debugging wrappers around
>> > jQuery core methods. You don't even need it
;consoled" or else you won't know anything about the
> context of the problem.
> Of course, I'm talking from the point of view of someone who develops sites
> that are ultra-heavy in the js department.
>
> 2009/5/19 David Zhou
>>
>> I wonder if it's fea
I wonder if it's feasible to monkeypatch debugging wrappers around
jQuery core methods. You don't even need it to throw errors -- a
simple console.log warning would suffice.
-- dz
On Tue, May 19, 2009 at 8:38 AM, Julian Aubourg
wrote:
> jquery.debug.js / jquery.release.js ? ;)
> I really lik
On Mon, Apr 20, 2009 at 8:09 AM, John Resig wrote:
>
>> 3. jQuery blows up when hosting webpage JS redefines createElement().
>> Thanks eBay, that was hilarious! This one would obviously affect any
>> JS bookmarklet, but it does indicate the "hostile" environment jQuery
>> could be operating in.
On Thu, Apr 16, 2009 at 12:48 AM, Pink Pig
wrote:
>
> On Apr 15, 7:11 pm, Ricardo wrote:
>> Try a search for '@' in the plugin files, it shouldn't be hard.
>>
>> On Apr 15, 3:59 am, Pink Pig wrote:
>>
>> > Maybe you guys should stop patting yourselves on the back long enough
>> > to straighten
Yup. From http://docs.jquery.com/Release:jQuery_1.3:
"The '@' in [...@attr] has been removed. Deprecated since 1.2 this old
syntax no longer works. Simply remove the @ to upgrade."
-- dz
On Fri, Apr 3, 2009 at 12:43 PM, Elijah Insua wrote:
> using @ to specify attributes was depricated in 1
On Fri, Apr 3, 2009 at 8:42 AM, Dev wrote:
>
Isn't tablesorter a plugin? You should probably contact the author
directly to see if it's a known bug and if he wants to integrate your
fix.
-- dz
On Fri, Apr 3, 2009 at 10:14 AM, Christian T.
wrote:
>
> Hi,
>
> I am a new user of TableSorter and just ran into a bug with sorting a
> digit c
Otherwise, I also tested on Firefox and Safari on OS X where there are
(I think) more accurate timers.
-- dz
On Thu, Apr 2, 2009 at 12:01 PM, David Zhou wrote:
> I booted into two dedicated Windows partitions that have IE6 and IE7
> installed respectively. This was on a Core 2 Duo 2
ould like to know if you used IE tester ( my choice ) rather than
> Multiple IE
>
> On Thu, Apr 2, 2009 at 4:17 PM, David Zhou wrote:
>>
>> I did, and it doesn't quite match up to your times -- which could be
>> due to machine differences or any number of reasons. P
n Thu, Apr 2, 2009 at 10:41 AM, Andrea Giammarchi
wrote:
> if you want to try the test you can visit this page:
> http://bill.dojotoolkit.org/taskspeed/
>
> or create a local TaskSpeed implementation
>
> On Thu, Apr 2, 2009 at 3:19 PM, David Zhou wrote:
>>
>> How man
How many times did you run your tests? Are these averages?
Also, did you try the tests on a non-Windows XP or Vista machine to
get more accurate results? (At least for Firefox and Opera).
I don't doubt that pure DOM manipulation is going to be faster, but
it's certainly surprising to see how muc
On Wed, Apr 1, 2009 at 2:08 PM, Ryura wrote:
>
> This is not great, its absolutely terrible. IE6 is the WORST browser
> on the web. I would have expected the jquery-dev list to be a bit more
> intelligent toward this matter. IE is slow and clunky. ActiveX is not
> a good feature, it is a major se
On Tue, Mar 24, 2009 at 4:29 PM, Dean Edwards wrote:
>
> On Mar 24, 8:09 pm, John Resig wrote:
>> Why would you want this?
>>
>
> It will stop plugins from interfering with each other.
>
> If a plugin has an error in its document.ready handler it will prevent
> subsequent handlers from running.
Emacs doesn't float everyone's boat -- and I'm a Vim user myself --
but the best javascript editing mode I've ever used or seen is
probably js2 mode in Emacs. I think it ties with IntelliJ at the very
least. YMMV.
-- dz
On Mon, Mar 16, 2009 at 4:59 AM, Mark Gibson wrote:
>
> Hey this looks
In terms of editors, I use vim for everything I do.
-- dz
On Fri, Mar 13, 2009 at 11:24 AM, chris thatcher
wrote:
> On windows I recommend 'e' which is a copy of 'textmate' which is my
> recommendation for mac. I bet textmate runs on linux in general but can't
> promise that.
>
> On Fri, Mar
In terms of patching jQuery core, I usually grab a build of the latest
revision, and work off that. Then backport changes to the svn
checkout to generate a diff.
As for testing random jQuery snippets, I've been eating my own
medicine and using the jQuery tester utility I wrote.
-- dz
On Thu,
Any other jQuery folks going to SXSW? I'll be there 'til Tuesday.
-- dz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To
To help with test cases, here are a couple tools to help with the boilerplate:
http://jquery.nodnod.net/
http://jsbin.com/
-- dz
On Tue, Feb 24, 2009 at 10:32 PM, John Resig wrote:
>
> The best technique to get started is to go in the bug tracker, find an
> open ticket and to produce a worki
I'm not sure I understand your question, but what about something like this:
var itemname1, itemname2;
$('.list-item').each(function(){
if (this.innerHTML.match(/Item Name/))
itemname1 = this;
if (this.innerHTML.match(/Item Name 2/))
itemname2 = this;
});
-- dz
On Sun, Feb 22,
Hi Hoai,
jquery-en is likely a better place for this sort of question:
http://groups.google.com/group/jquery-en
But in response to your question, does the following from jQuery's
documentation not work for you?
$("#feeds").load("feeds.html");
-- dz
On Sun, Feb 22, 2009 at 1:31 AM, HK007 w
http://dev.jquery.com/ticket/4165 -- sounds like he needed to use live events.
http://dev.jquery.com/ticket/4159 -- invalid
http://dev.jquery.com/ticket/4158 -- patch of fix discovered by initjh
Thanks!
-- dz
--~--~-~--~~~---~--~~
You received this message becaus
http://media.nodnod.net/test.html works for me. Is it because I'm not
serving the page as application/xhtml+xml?
-- dz
On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin wrote:
>
> Me too.
>
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/
> 2009011913 Firefox/3.0.6 (.NET CLR
In that link, I see the alert from catch in Firefox 3 with the same
failure code that David mentioned earlier.
-- dz
On Fri, Feb 13, 2009 at 9:15 AM, John Resig wrote:
>
> I've set up a test page and no possible combination that I try works:
> http://dev.jquery.com/~john/ticket/xmlns/
>
> In
ue that as just general
changes in the upgrade.
-- dz
On Thu, Feb 12, 2009 at 10:31 AM, David Zhou wrote:
> I wonder if it would be helpful to have a backwards incompatible
> changes section for every jQuery release, and a master page somewhere
> collating all those changes. The
I wonder if it would be helpful to have a backwards incompatible
changes section for every jQuery release, and a master page somewhere
collating all those changes. The changes are usually highlighted in
the release notes, but it'd be more clear if there was a section
specifically calling out the
Couldn't you just do:
jQuery.fn.and = function(sel){
return this.length? this.add(sel) : jQuery([]);
};
-- dz
On Tue, Feb 10, 2009 at 8:57 PM, Dave Methvin wrote:
>
>> If you want to work on the elements, though, the .and()
>> plugin will return either [] or [#field1, #field2]
>> to the c
That would return a boolean value, not the length.
-- dz
On Mon, Feb 9, 2009 at 1:59 PM, Ricardo Tomasi wrote:
>
> Wouldn't that be essentially the same as $("#field1, #field2").length
> == 2 ?
>
> On Feb 9, 1:35 am, Dave Methvin wrote:
>> > $("#field1 & #field2").length would be either 0 or
That would be pretty sweet. But in the mean time, Jorn, maybe you
could use something like:
jQuery.fn.ifFound = function(condition) {
return (this.length === condition)?this:jQuery([]);
}
So you could do $('#field1, #field2').ifFound(3).length
-- dz
On Sun, Feb 8, 2009 at 5:39 AM, Daniel
r-point.com)
> -Wiki-Tools (http://wiki-tools.com)
> -MonkeyScript (http://monkeyscript.nadir-point.com)
> -Animepedia (http://anime.wikia.com)
> -Narutopedia (http://naruto.wikia.com)
> -Soul Eater Wiki (http://souleater.wikia.com)
>
>
>
> David Zhou wrote:
>> While that&
Nadir-Seen-Fire) [http://nadir-seen-fire.com]
> -Nadir-Point (http://nadir-point.com)
> -Wiki-Tools (http://wiki-tools.com)
> -MonkeyScript (http://monkeyscript.nadir-point.com)
> -Animepedia (http://anime.wikia.com)
> -Narutopedia (http://naruto.wikia.com)
> -Soul Eater Wiki (htt
We have a pretty solid policy in jQuery: Any feature that we
>> guarantee that it'll work in every browser that we support. That
>> pretty much cuts out border radius, for now. But yeah, a plugin would
>> be great here.
>>
>> --John
>>
>>
>>
&
Wouldn't this be better as a plugin?
-- dz
On Sun, Feb 8, 2009 at 12:03 AM, Daniel Friesen
wrote:
>
> Both Mozilla and WebKit have built support for border radius (meaning
> now only IE and Opera should be left without this kind of feature):
> Mozilla with -moz-border-radius and -moz-border-
ss('background-color', 'red');
});
That avoids fetching parent() twice.
-- dz
On Fri, Feb 6, 2009 at 7:44 PM, David Zhou wrote:
> Hmm, what about:
>
> $(function() {
>var selection = $(".container");
>var target = $("a:first");
&g
tainer = this;
>return targetParents.filter(function() { return this == container;
> }).length;
> });
> filtered.css("background-color", "red");
> });
>
> That selects the target's parents once, and filters them once for each
> container, which
_d");
return false;
}
-- dz
On Fri, Feb 6, 2009 at 10:43 AM, Jörn Zaefferer
wrote:
>
> Nope, that isn't it. My example is simplified, and the target comes an
> event triggered elsewhere. So target is just a reference to a DOM
> element, and can't be replaced
Isn't that basically:
if ($('.container a:first').length)
$('.container').css('background-color', 'red');
Unless I misunderstand what you're asking for?
-- dz
On Fri, Feb 6, 2009 at 6:58 AM, Jörn Zaefferer
wrote:
>
> I'm trying to solve the follow selector problem: Assuming two
> contai
On Wed, Feb 4, 2009 at 11:10 AM, Paul Bakaus wrote:
>
> On Wed, Feb 4, 2009 at 6:35 PM, ajp wrote:
>>
>> - Even though STYLE is supposed to live in the HEAD all browsers are
>> happy to have as many style elements sprinkled around as you like. All
>> the styles will be applied as you'd expect.
On Mon, Feb 2, 2009 at 11:24 PM, Sam Minnee wrote:
> Is there any way of doing this kind of debugging in jQuery? Or are
> there other solutions to this debuggability problem? Perhaps I'm
> structuring my code in an inappropriate way?
Check out Visual Events:
http://www.sprymedia.co.uk/articl
I don't have IE8 at hand, but here's a test case with the code above:
http://jquery.nodnod.net/cases/95
-- dz
On Tue, Feb 3, 2009 at 9:00 AM, John Resig wrote:
>
> Do you have a sample page that we can look at? I'm not sure what the
> issue is - it may be a problem with IE 8.
>
> --John
>
>
Er.. a class with a space is two separate classes.
-- dz
On Thu, Jan 29, 2009 at 4:01 PM, rhasson wrote:
>
> I run this command $("^.WasPrice") which suppose to find the class
> that starts with WasPrice. The actual class name is "WasPrice
> PriceM". My issue is being to select a class with
s
>>
>>
>>
>> wrote:
>>
>> > just tried the lastest nightly build, still got no luck...
>>
>> > On 1月28日, 上午3時09分, helianthus wrote:
>> >> Tried that, same result...
>>
>> >> On 1月28日, 上午3時07分, David Zho
What you're saying essentially boils down :
if test_standard:
standard
else if test_alternate:
alternate
else:
something
And for the something, you say: "blow up or do nothing or return false
or something".
jQuery does:
if test_standard:
standard
else:
alternate
It seems like you're
On Wed, Jan 28, 2009 at 10:30 AM, John Resig wrote:
> It doesn't matter - one way or the other the broken browser is still
> going to be broken - the only difference is that IE is going to be
> slower.
I think most of this was hashed over in a prior thread, but the only
functional difference I
t; On Jan 28, 2009, at 9:27 AM, Karl Swedberg wrote:
>
> no prob. glad you brought it up. another closed bug is a good thing! I'll
> close it.
>
> --Karl
>
> Karl Swedberg
> www.englishrules.com
> www.learningjquery.com
>
>
>
> On Jan 28, 2009
on.selected ) {
> // Get the specifc value for the option
> value = jQuery(option).val();
>
> --Karl
>
> Karl Swedberg
> www.englishrules.com
> www.learningjquery.com
>
>
>
> On Jan 28, 2009, at 4:24 AM, David Zhou wrote:
>
> http://dev.jquery.com/
http://dev.jquery.com/ticket/3104
Seeing as last activity was around 4 months ago, is this still being
worked on? I was thinking about working on a patch, but was unsure if
someone had decided to leave the behavior as it currently is.
-- dz
--~--~-~--~~~---~--~~
He's talking about YASS. The code is here:
http://code.google.com/p/yeasss/source/browse/trunk/src/yass.js
The speed claims are interesting if true, though it looks like it's
still using browser sniffing.
-- dz
On Tue, Jan 27, 2009 at 4:06 PM, Elijah Insua wrote:
> link is broken.
>
> On T
What happens if you use the full un-minified version?
-- dz
On Tue, Jan 27, 2009 at 1:54 PM, helianthus
wrote:
>
> I hope I know why this happens...
> Just tried again, no error is shown at the error console, but the
> problem still exists.
>
> On 1月28日, 上午2時46分, John Resig wrote:
>> I really
This is already in the bug tracker as #3988:
http://dev.jquery.com/ticket/3988
-- dz
On Tue, Jan 27, 2009 at 11:24 AM, John Resig wrote:
>
> Do you have a demo page that we can look at?
>
> --John
>
>
>
> On Fri, Jan 23, 2009 at 11:01 AM, helianthus
> wrote:
>>
>> 1.2.6:
>> No problems on
k. At some point there will be an
> actual release, probably combined with a blog post, so you'll know
> when its done.
>
> Jörn
>
> On Fri, Jan 23, 2009 at 12:15 PM, David Zhou wrote:
>>
>> Sure, I can add it in. Are there releases of QUnit or do you
>> typi
3, 2009 at 3:56 AM, David Zhou wrote:
>>
>> Partially out of personal laziness in manually creating test cases
>> with the same boilerplate over and over again, I made a really simple
>> app that'll help that process along.
>>
>> http://jquery.nodn
Partially out of personal laziness in manually creating test cases
with the same boilerplate over and over again, I made a really simple
app that'll help that process along.
http://jquery.nodnod.net/
For example, here's a sample case:
http://jquery.nodnod.net/cases/7
The dropdowns allow easy s
On Wed, Jan 21, 2009 at 10:50 AM, John Resig wrote:
>
>> when i ran into this issue, i repacked it using the current version of
>> Packer for shits and giggles before sending Dean Edwards a bug report,
>> and it worked just fine. what Packer version are you guys using, John?
>
> We don't provide
If the behavior of hide or other functions bother you,there's no
reason why you can't override those methods with your own in, say,
jquery-customized.js that you include after jquery.js.
You can also do it similarly for other stuff that bothers you.
There's already an "API" to the backend, in tha
I have a feeling it's related to http://dev.jquery.com/ticket/3873 --
especially with the two .testing classes on the span and div.
On Fri, Jan 16, 2009 at 2:40 PM, John Resig wrote:
>
> Thanks for the test case - I'll be looking in to it!
>
> --John
>
>
>
> On Fri, Jan 16, 2009 at 2:02 PM, Rein
does not have the attribute
>>>> >> itself": li:not([class=zoom]) it seems like an acceptable change.
>>>>
>>>> >> --John
>>>>
>>>> >> On Thu, Jan 15, 2009 at 8:50 AM, prefect
>>>> >> wrote:
>>>>
Somewhat related, there's a small but harmless typo at
http://dev.jquery.com/browser/trunk/jquery/src/core.js#L479
Is that supposed to be "return this.slice( i, i + 1 )" ?
On Thu, Jan 15, 2009 at 2:07 AM, David Zhou wrote:
> It looks like a bug in Sizzle -- specifically, whe
an issue with :eq().
>>
>> Demo test case http://jsbin.com/omobe
>>
>> >
>>
>
> >
>
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development"
12:34 AM, Matt wrote:
>
> On Jan 14, 10:52 pm, "David Zhou" wrote:
>> Can you elaborate on these concepts?
>
> Simple. Don't make the assumption that if the standard approach
> doesn't work, then a specific fix will. That's almost as bad as saying
On Wed, Jan 14, 2009 at 11:39 PM, Matt wrote:
>
> On Jan 14, 3:11 pm, "David Zhou" wrote:
>> A new browser to be support would be enough to warrant a new version
>> of jQuery, I think.
>
> Which would be entirely unnecessary if feature detection is done
>
_state_id').val() )
>>
>> and the alert is "" so no value was set. I am 100% sure that 2 is in
>> the list of options for #usa_reference_state_id.
>>
>> >
>>
>
> >
>
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~-
ess. i first noticed that it was strange that the
>>> "single select" example for val() contains no "value" attributes, and
>>> instead returns text() if they are not
>>> present.http://docs.jquery.com/Attributes/val
>>>
>>
'd be
relatively trivial to do:
if supports_ standard
standard
else if supports_other_method
other_method
else
other_method2
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
;
>}
>}
>})
>.find('li')
>.bind('focus', function() {
> $(this).addClass('has-focus'); })
>.bind('blur', function() {
&
>
> On Wed, Jan 14, 2009 at 6:45 AM, John Resig wrote:
>>
>> Hey Everyone -
>>
>> jQuery 1.3 is out! Full details here:
>> http://blog.jquery.com/2009/01/14/jquery-13-and-the-jquery-foundation/
>>
>> Happy 3rd Birthday, jQuery!
&
st weaned
itself away from having explicit browser detection. Is it a good idea
to put it back into core for something like this?
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
ent);
>>>>> return options.length > 0 && ( element.type == "select-multiple" ||
>>>>> ($.browser.msie && !(options[0].attributes['value'].specified) ?
>>>>> options[0].text : options[0].value).length > 0);
>>>>>
>
id ] )
>> jQuery.cache[ id ] = {};
>>
>> // Prevent overriding the named cache with undefined values
>> if ( data !== undefined )
>> jQuery.cache[ id ][ name ] = data;
>>
>> // Return the n
86 matches
Mail list logo
