> It's always a good idea to either use a ||'' or cast your data to a string or
> other proper datatype when using jQuery, a large number of the methods will
> have somewhat undesirable results if you try using null or undefined, it's a
> known issue.
Oh, I wouldn't go that far. We've patched
It'll be pretty hard to do that since (cross-domain) JSONP uses a
completely different means of communicating from the normal Ajax
request (creating script tags and letting the scripts load and
execute).
We have a lot more power when it comes to using XMLHttpRequests and
working against a local d
That's a great set of patches - thanks! The only minor nit that I see
is that you do:
jQuery.ajaxSetup({ ifModified: true });
In your tests instead of putting the setting inline in the $.ajax()
call (which would probably be preferred, since it'll be less likely to
affect other tests). I made the
This is due to the issue where if an element has a height or width
equal to 0, in IE in quirksmode, the full height/width of the element
is shown. jQuery use to have a fix for this - anytime a value of 0 was
set a value of 1 was set instead - unfortunately this caused other
strange side-effects wi
Hmm, I don't have an explanation, off-hand. Could you file a ticket
with your test files attached? Thanks!
http://dev.jquery.com/newticket
--John
On Thu, Jun 11, 2009 at 3:33 PM,
morgancodes wrote:
>
> Hello,
> No response to this question on jquery users list or stackoverflow, so
> I'm trying
A newer one may help you - but it's very likely that it's the other,
older, libraries that are manipulating the native object prototypes
(namely Prototype and Scriptaculous) are the cause of the problem.
--John
On Tue, Jun 9, 2009 at 6:15 AM, rimmer333 wrote:
>
> Hello.
>
> I'm working on a re
I can't think of a single thing that we could remove from jQuery that
wouldn't also affect IE 7.0. The JavaScript and DOM implementations in
IE 6 and 7 are virtually identical - and because of that there's
really no reason for us to stop actively supporting IE 6 (at least not
until both 6 and 7 ar
I only ask that the jQuery.isFunction(val) results be cached to avoid
repeated calls for the function check - but other than that, sounds
good.
--John
On Wed, Jun 3, 2009 at 1:32 PM, Yehuda Katz wrote:
> I'd like to submit a patch that lets all setters (val, html, text, etc.)
> take a functio
David -
It'd be good to file a ticket on the issue and add in your patch and a
link back to this discussion:
http://dev.jquery.com/newticket
How well have you tested the change across browsers? Does changing
.className to .getAttribute/setAttribute("class") have any other
ramifications? It's def
Do you have a page that we can view to reproduce the problem? (That would
help a lot)
Otherwise, do you have a stack trace from where the bug is occurring?
--John
On Thu, May 28, 2009 at 12:00 AM, Bob wrote:
>
> Hi,
> I have recently upgraded from jQuery 1.2 to the current latest
> (1.3.2).
>
I don't think so - I've updated the documentation to be a little more
precise.
http://docs.jquery.com/Attributes/val
--John
On Tue, May 26, 2009 at 3:26 PM, Alex Farcas wrote:
>
> I noticed val() ignores the 'value' attribute on html elements.
>
> If i have this markup:
> < div id="test" value
JSONP cross domain requests only work for JSONP-formatted data.
Unfortunately it's not possible to grab raw HTML in a truly cross-domain
manner.
You may also want to check the error console, sometimes errors don't show up
in Firebug.
--John
On Sun, May 24, 2009 at 7:15 AM, Toreddo wrote:
>
>
What would these properties be used for?
--John
On Fri, May 22, 2009 at 5:21 PM, Ralf Stoltze
wrote:
>
> Hi,
>
> in order to simplify usage of my hoverFlow plugin, I'd like to have
> access to the animation properties object used by jQuery's shortcut
> animations like slideDown/slideUp.
>
> Thi
logically or practically sense :-)
>
> quick patch, remove new, just Function(whatever)();
>
>
>
> On Wed, May 20, 2009 at 10:29 PM, John Resig wrote:
>
>> Ticket filed:
>> http://dev.jquery.com/ticket/4680
>>
>> Fix landed:
>> http://dev.jquery.com/
Ticket filed:
http://dev.jquery.com/ticket/4680
Fix landed:
http://dev.jquery.com/changeset/6361
--John
On Wed, May 20, 2009 at 10:24 AM, John Resig wrote:
> Ok, it all sounds in order to me - someone want to file a ticket?
> http://dev.jquery.com/newticket
>
> --John
>
>
nction evaluate( data ){
>return Function("return "+( data ) )();
>};
>
> })();
>
> becomes...
>
> (function(){function A(B){return Function("return "+(B))()}})();
>
>
> On May 20, 9:06 am, John Resig wrote:
> > Has anyo
for to always return the same object. Unfortunately
>> this is not a real world case.
>>
>> On May 20, 2009 7:33 AM, "Michael Geary" wrote:
>>
>> Function( 'return ' + data )() is also MUCH faster in Firefox than eval.
>>
>> In a
that are not globals )
>
>
> On Tue, May 19, 2009 at 11:32 PM, John Resig wrote:
>
>> That's specifically being done to allow YUIMin to properly compress jQuery
>> (it sees an eval and assumes that it can't be compressed, but using that
>> technique allows it to
That's specifically being done to allow YUIMin to properly compress jQuery
(it sees an eval and assumes that it can't be compressed, but using that
technique allows it to work).
--John
On Tue, May 19, 2009 at 5:22 PM, Justin Meyer wrote:
>
> I assume there must be a good reason, but why is wind
May want to look at this as well:
http://planet.jquery.com/
--John
On Tue, May 19, 2009 at 2:26 PM, jquerypla...@gmail.com <
jquerypla...@gmail.com> wrote:
>
> hello people
>
> i started a new project called jplanet. it's a content aggregator
> about jquery.
>
> see more in http://jplanet.tumbl
Jason -
I'm not sure if this is something that we want to handle, specifically
(especially since that method has already been removed in current versions
of Prototype).
--John
On Mon, May 18, 2009 at 1:27 PM, Jason Persampieri wrote:
>
> (Solution found... more info provided for future searche
This change looks good - it'll probably take a perf hit in some cases, but
that seems to be ok, since those cases were causing problems anyway (such as
when the contents are floated outside of the element).
--John
On Mon, May 18, 2009 at 9:54 AM, Brandon Aaron wrote:
>
> Unfortunately checking
To be clear - Firefox is returning an element - the bug is that
doing typeof on an element returns function in jQuery (but it is,
in fact, not a function). It's just a silly bug in Firefox, everything still
works as you would expect it to.
--John
On Sat, May 16, 2009 at 12:46 PM, stephb...@goo
I'm confused - why are you attaching the QUnit.done/log handlers inside
window.onload? Ideally they should be the very first thing done (after
loading the test suite itself).
--John
On Tue, May 12, 2009 at 10:59 PM, chris thatcher <
thatcher.christop...@gmail.com> wrote:
> I noticed we where us
Hmm, yeah, I think that's probably a bug, as it stands. Could you file a
ticket?
--John
On Thu, May 7, 2009 at 11:34 PM, Jeffery To wrote:
>
> Hi,
>
> Going through the test suite (with jQuery 1.3.2), I noticed that there
> is a selector test for "div div:eq(27)". Trying the query in Firebug
>
It's not completely clear what your code does or how it would be used, from
looking at it - do you have any examples?
--John
On Mon, May 4, 2009 at 7:43 PM, Robert Katić wrote:
>
> After some readings on the "A Modest Proposal: jQuery Enterprise"
> discussion at
> http://groups.google.com/grou
:
>
> So did document ready not wait for CSS to load in 1.2.6 then? When Brandon
> mentioned that it made sense to me because people started complaining
> about the problems with jScrollPane shortly after 1.3 was released...
>
> On Fri, 01 May 2009 19:53:21 -0700, John Resig wrote:
&
Unfortunately, it's not that easy - I wasn't able to find a set of
techniques that worked in all browsers that waited for all CSS to load (save
for the window onload event).
If anyone has any insight, I'd appreciate it.
--John
On Fri, May 1, 2009 at 4:27 PM, Kelvin Luck wrote:
>
> Hmmm... The
Hmm - good point, there's no way to do that right now.
Could you file a ticket on it?
http://dev.jquery.com/newticket
--John
On Mon, Apr 27, 2009 at 2:03 PM, Jack Bates wrote:
>
> How can I do an AJAX request with jQuery and *not* add the X-Requested-
> With header?
>
> I am trying to do a cr
What version of qUnit are you using? You can just hook in to QUnit.done and
it gets called when the tests are done running.
--John
On Sun, Apr 26, 2009 at 7:52 AM, Miquel wrote:
>
> I am after a way to better integrate Qunit into a continuous
> integration system. I need quinit to send a repor
This should go in a new thread.
--John
On Fri, Apr 24, 2009 at 4:54 PM, Michael Park wrote:
>
> There is definitely a problem with the way jQuery (I'm using 1.3.2)
> handles cleaning up namespaced events (I'm tracing the 'unload' event
> codepath). The problem from what I can tell seems to be
Hmm... I do understand your predicament (wanting the
dynamically-loaded script to use the right version of jQuery). I'm
trying to imagine situations where your change could cause potential
problems, but I'm not sure, yet.
FWIW, this problem also affects getScript when pulling scripts from an
outs
Actually, r6310:
http://dev.jquery.com/changeset/6310
Thanks Brandon.
--John
On Tue, Apr 21, 2009 at 2:53 PM, Brandon Aaron wrote:
>
> FYI... I just committed r6130 a fix for the memory leaks at runtime.
> Please let me know if you find anymore leaks.
>
> --
> Brandon Aaron
>
>
> On Apr 16,
It sounds like this question would be better suited to the jquery-en group:
http://groups.google.com/group/jquery-en
You should re-post your message there and be sure to include a URL to
a page where the problem is occurring - thanks!
--John
On Tue, Apr 21, 2009 at 2:14 AM, KhanZeeshan wrote
> 1. JQuery blows up when hosting webpage JS has added attributes to
> Object.prototype. I fixed this by patching jQuery for-in loops as
> discussed in: http://dev.jquery.com/ticket/2721
Yeah, this is still something that we're hoping to fix at some point.
> 2. JQuery blows up on certain xhtml+x
show animates the height and width of the element and inline elements
can't have a height or width. I recommend using fadeIn instead (since
that doesn't touch height/width) or making the element display: block
with a CSS float of left.
--John
On Thu, Apr 16, 2009 at 3:08 AM, Raxit wrote:
>
>
Hmm - I wonder if it has to do with the attachEvent that we're testing.
If you comment out these lines, does the leak still exist?
if ( div.attachEvent && div.fireEvent ) {
div.attachEvent("onclick", function(){
// Cloning a node shouldn't copy over
It seems like it'd be easy to special-case POST requests to make sure
that an empty string was sent. Could you file a bug on the issue?
Thanks!
--John
On Thu, Apr 16, 2009 at 9:38 AM, Rebecca Murphey wrote:
>
> The issue didn't occur in IE; I haven't tested in C or S.
>
> As far as POSTing wi
Are you sure you're not using some plugin that's including that symbol?
--John
On Mon, Apr 13, 2009 at 4:24 PM, Pink Pig
wrote:
>
> On Apr 13, 8:34 am, Leonardo K wrote:
>> *From jQuery site:
>>
>> Note:* In jQuery 1.3 [...@attr] style selectors were removed (they were
>> previously deprecat
;m currently on #jquery-dev channel if you would like to ask me
> something there.
> Thanks again
> Julián
>
> On Apr 5, 12:43 am, John Resig wrote:
>> Could you test with a nightly? It's likely that this was already
>> fixed.http://code.jquery.com/nightli
Could you test with a nightly? It's likely that this was already fixed.
http://code.jquery.com/nightlies/jquery-2009-03-26.js
--John
On Sat, Apr 4, 2009 at 11:38 PM, Julián Landerreche wrote:
>
> Hi again,
>
> this bug seems to affect just Webkit (Safari/Chrome) browsers.
> The thing have bee
Sure, I think that's reasonable - thanks for the code. I've already
been working to remove most usage of .each() internally, in jQuery,
for 1.3.3 so this should be a simple change to add in once that's
done.
--John
On Fri, Apr 3, 2009 at 5:14 PM, Matt wrote:
>
> This is the current .each() fu
Which aspect? Do you have a demo?
--John
On Fri, Apr 3, 2009 at 2:46 PM, sfearl1 wrote:
>
> this has still not been fixed
>
> On Mar 3, 9:34 am, Már Örlygsson wrote:
>> > What version of jQuery/Sizzle are you using? A lot of clean-up was
>> > done recently.
>>
>> Ah... this may very well hav
Yep, that's precisely it. We have a couple PHP scripts which can be
made to spit back different things (XML, HTML, text) and add various
delays to simulate network traffic. We don't include cross-domain
tests but that's mostly because we'd rather not rely on the quality of
someone else's server/ne
> Otherwise, I also tested on Firefox and Safari on OS X where there are
> (I think) more accurate timers.
You are correct:
http://ejohn.org/blog/accuracy-of-javascript-time/
--John
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
e can't do for 1.3.3.
--John
On Tue, Mar 31, 2009 at 10:28 AM, Jakub Suder wrote:
>
> On 31 Mar, 15:40, John Resig wrote:
>> We've made some changes to the logic in the nightlies - does the
>> change help your case?http://code.jquery.com/nightlies/jquery-2009-03-26
We've made some changes to the logic in the nightlies - does the
change help your case?
http://code.jquery.com/nightlies/jquery-2009-03-26.js
--John
On Tue, Mar 31, 2009 at 8:42 AM, Jakub Suder wrote:
>
> Hi,
>
> In my project, I have a box whose contents are partially hidden, and
> the botto
If I'm understanding the problem correctly, you'll want this:
$(".gallery img").clone().appendTo("#bild_spel div ul").wrap("");
(remove the .clone() if you want to move the img elements, as well)
--John
On Mon, Mar 30, 2009 at 6:48 AM, smurkas wrote:
>
> Hello.
>
> I have a situation where
Actually, I think this one was already fixed.
Can you test it real quick?
http://code.jquery.com/nightlies/jquery-2009-03-26.js
--John
On Mon, Mar 30, 2009 at 8:24 AM, yodza wrote:
>
> Hi,
>
> From 1.3.1 to 1.3.2 sibling selector does not work anymore:
> http://jquery.nodnod.net/cases/277
>
No, we don't have it on a definite timeline.
--John
On Thu, Mar 26, 2009 at 11:11 PM, hassafrass wrote:
>
> Hmm, any idea when that release will be :-) ?
>
> On Mar 26, 1:27 pm, John Resig wrote:
>> Correct, this is an issue with strict mode. It's something tha
First, please don't use all-caps in your email subjects.
Second, Yes, this is known - and it's highly recommended that you
don't extend Object.prototype - it'll do far more than break jQuery.
Third, it's something that we're looking into for the future, but
please don't do it, regardless of the
Correct, this is an issue with strict mode. It's something that we're
looking to tackle in an upcoming release.
--John
On Thu, Mar 26, 2009 at 3:38 PM, hassafrass wrote:
>
> updated to 1.3.2 same problem.
>
> On Mar 26, 11:45 am, hassafrass wrote:
>> Also if I change strict warnings in Firef
A couple ways:
$(this).find("> span")
or $(this).children("span")
or $("> span", this)
The second one will probably work best.
--John
On Thu, Mar 26, 2009 at 9:41 AM, hamazasp.avetisyan
wrote:
>
> Hi,
>
> Let's look at this sample
>
> $("div > span").css("border", "3px double red");
>
> This
I'm not seeing an issue off-hand - could you simplify the code that
you're trying to execute? For example, does this error only occur if
getScript is used?
--John
On Thu, Mar 26, 2009 at 7:15 AM, Gilles wrote:
>
> Hi,
>
> I normally bebug my code myself, cos I believe it helps me improve
> my
Hello -
Interesting work, congrats!
A couple quick points:
Kind of disconcerting that it's actually not being integrated into
another library - that's where much of the hard part comes from (and
speed degradation).
It's also curious because the MooTools team complained when I compared
Sizzle t
> @John Resig - Your try-finally block fails in IE6 because of this bug:
> http://webbugtrack.blogspot.com/2007/11/bug-184-catch-to-try-catch-finally-in.html
Ah, interesting - thanks for the heads-up.
--John
--~--~-~--~~~---~--~~
You received this m
setTimeout(runHandlers);
> throw e;
> }
> }
>
> var handlers = [
> function(){
> throw "A";
> },
> function(){
> throw "B";
> }
> ];
>
> This one will throw both (all) errors.
>
> Am I missing something?
>
>
> The point is, you cant move your mouse fast enough, or type so
> quickly, that your event dispatch system is going to get in the
> way. :-)
It won't explicitly "get in the way" but it will certainly contribute
to un-needed overhead. Right now we're fighting tooth-and-nail to
squeeze every bit o
> It doesn't break like that in MSIE as you well know.
How so? I fired up my copy of IE 8 and the Script Debugger worked
great - broke right on the throw breakpoint - virtually identical to
Firebug (I'm really enjoying the new developer tools in IE 8).
> What are you measuring here? Think about
> That's pretty neat code. But if I have an error in JavaScript then I
> prefer the code to break where the error is. If I was using a debugger
> to inspect the stack then I wouldn't be able to debug this because the
> error has passed.
That's not true, observe:
http://ejohn.org/files/handler-bre
> Won't you get only the latest exception thrown or will you get all the
> exceptions? I never used exceptions that intensely in javascript.
Good question - in the dummy code that I posted it appears that only
the last one goes into the try/catch - but if you think about it, that
makes sense sinc
> I don't think it is the resposibility of the dispatcher to handle
> exceptions.
> I think it it is the resposibility of the dispatcher to dispatch
> events. :-)
> An error in one handler should not prevent another handler from
> executing.
> Nor should a dispatcher suppress errors so that it can
> 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. A bad plugin can affect other jQuery
> code.
I don't buy that argument. If a plugin or other jQuery method is
malfunctioning then
I don't understand the point of it - so you have code that throws an
exception (obviously indicating that something is broken) and you
expect it to do what... still try to run? Exceptions are the universal
indicator that something is broken and not working. I understand his
implementation but he d
> .unbind() .unbind(type); .unbind(type, func);
> Using .unbind(func); seams the most logical since the pattern looks like
> you're just ommitting whatever you aren't specifying specifically.
>
> What would "*.foo" do?
Unbind everything that has that namespace.
http://docs.jquery.com/Namespaced_E
-Tools (http://nadir-point.com) (http://wiki-tools.com)
> -MonkeyScript (http://monkeyscript.org)
> -Animepedia (http://anime.wikia.com)
> -Narutopedia (http://naruto.wikia.com)
> -Soul Eater Wiki (http://souleater.wikia.com)
>
> John Resig wrote:
> > And how is the natural he
I remember someone mentioning something like:
.unbind("*", fn)
It could also apply to other things like:
.unbind("*.foo", fn)
.bind("*", fn)
--John
On Sat, Mar 21, 2009 at 6:16 PM, Daniel Friesen
wrote:
>
> Originally the lead programmer wanted to avoid making the core of the
> applicati
Probably, yeah - could you file a ticket?
--John
On Sat, Mar 21, 2009 at 1:57 PM, David Citron wrote:
>
> Internet Explorer does not accept the attribute "colspan" and instead
> requires "colSpan" with a capitol 'S'.
>
> jQuery.props already has a mapping for "rowspan" -> "rowSpan".
>
> Should
And how is the natural height determined if you've already explicitly
overwritten it with another value?
--John
On Fri, Mar 20, 2009 at 9:11 PM, Daniel Friesen
wrote:
>
> At work I tried to animate something to grow horizontally then grow
> vertically.
>
> .hide().css({height: 5}) // Use a smal
You want .val():
http://docs.jquery.com/Attributes/val
In the future, a question like this should be posted to the jQuery mailing
list:
http://groups.google.com/group/jquery-en
--John
On Thu, Mar 19, 2009 at 8:38 AM, pdoddamani wrote:
>
>
> Hi
>
> id="playlistbuilder">
>
>
This was an intentional change. We changed the meaning of :visible to mean
"elements that aren't visible" (this includes elements that have a height
and width of 0 - and thus aren't visible to the user). This resulted in a
massive speed-up.
We discussed this in the release notes:
http://docs.jque
Well, VML is a mess in IE - it's probably something as simple as trying to
access a property and that's causing it to explode. You should add your test
case to the existing bug (at least then we can have some more information to
go off of).
In the meantime I'd try and be more specific in your sele
Would you be open to filing a bug on this? Thanks.
What a stupid behavior on the part of IE.
--John
On Tue, Mar 17, 2009 at 3:35 AM, Danny wrote:
>
> $.each(document.styleSheets... fails with the error:
> Line: 692
> Character: 11
> Code: 0
> Error Message: Invalid procedure call or argument
Good question - I'm about 75% certain that no callbacks get called
(without taking a look at the code). Although, I'm sure a quick test
could confirm/deny that.
--John
On Thu, Mar 12, 2009 at 10:49 PM, Julian Aubourg
wrote:
> Working on a jsonp plugin (that will supercede my getJSON mess of a
g forward to checking out
>> the list. Good luck as far as the application goes!
>>
>> On Mar 4, 5:29 am, John Resig wrote:
>>
>> > Yep, we're planning on it! We're pulling together our list of projects
>> > right now, in fact.
>>
>>
Not hugely surprised - is invalid HTML (since
elements don't have a closing tag) - I think all bets are off at that point.
--John
On Thu, Mar 12, 2009 at 12:51 PM, Troop4Christ wrote:
>
> So today I was creating a checkbox element in jQuery when I noticed
> that I had a typo in my code.. I h
This is something that we're looking in to for a future release, in the
meantime, you should definitely be using json2.js:
http://json.org/json2.js
--John
On Thu, Mar 12, 2009 at 2:27 AM, nothize wrote:
>
> I've found an old thread talking about the compatibility issue with
> json.js and jquer
I'm arriving on Friday, leaving Sunday - hope to see others there!
--John
On Thu, Mar 12, 2009 at 12:35 AM, David Zhou wrote:
>
> Any other jQuery folks going to SXSW? I'll be there 'til Tuesday.
>
> -- dz
>
> >
>
--~--~-~--~~~---~--~~
You received this message
Huh, that's bizarre. Could you file a quick bug on this?
http://dev.jquery.com/newticket
Thanks for all the hunting on this, I'll see if we can land something for
1.3.3.
--John
On Tue, Mar 10, 2009 at 8:00 PM, Stephen McKamey wrote:
>
> I've spent way too long on this, but I was convinced tha
Try this instead:
// we will add our javascript code here
$(document).ready(function(){
$("a").click(function() { alert("Hello world!"); });
});
--John
On Tue, Mar 10, 2009 at 10:43 AM, rayglaser wrote:
>
> I am sory to say that the getting started with JQuery Hello World
> example doe
Yeah, a ticket would be good - thanks!
--John
On Tue, Mar 10, 2009 at 8:37 AM, Bohdan Ganicky
wrote:
>
> Hi all,
>
> I have this selector: $("div:has(.help:not(.fixed))") looking for the
> first only:
>
> ...
> Help
> ...
>
>
> ...
> Help Fixed
> ...
>
>
> It worked just fine in ev
In the first case you're inserting the link into all the elements that
have a class of toggle - thus when you attach the click event it also
captures the events from the link. The second one insert the link
*before* the elements with a class of toggle, which doesn't bind any
event to it.
What you
I assume you mean your test suite - I would only have to guess that
whatever is bound to mouseup calls getJSON 8 times.
--John
On Sat, Mar 7, 2009 at 5:15 PM, John Teague wrote:
> This test is the eighth test in the suite and it gets executed 8 times. Any
> idea why?
>
> test("should retreiv
Unfortunately, I have no idea - it doesn't make it easier that it's
such a custom set up. Maybe someone with more iPhone dev experience
can speak to the situation.
--John
On Thu, Mar 5, 2009 at 4:52 PM, Parand wrote:
>
> Hello,
>
> I'm having a strange issue using jQuery on UIWebComponent on
Well, to be clear, this section of the jQuery code probably isn't
ready for this expansion yet - I'm going to be refactoring the
attribute/css code and will be splitting apart (giving you access to
the element, as well). I was planning on landing some of the custom
attribute/css property hooks the
I'm not sold on this. We were discussing the cloning of data recently,
it seems like this should be sufficient:
.clone(true) - Clone events and data (which is reasonable,
considering that events are part of data)
.clone(false) - Clone just elements (no data)
As far as removeID goes, it seems
There's really no need to branch out a whole project like this. If you
have a patch to add some extensibility (make it easier to handle
oddball CSS properties, for example) I'd definitely imagine that
something like that would be accepted, no problem. Just make a patch,
file a ticket, then post it
It's supposed to be - and this was a change in Firebug, not in jQuery
- it was actually a regression in Firebug that this no longer worked.
--John
On Wed, Mar 4, 2009 at 7:25 PM, Ricardo Tomasi wrote:
>
> Why is it that Firebug reports jQuery objects as simple arrays in
> 1.3.2? 1.2.6 always
Sounds reasonable. You should file a bug with this information attached:
http://dev.jquery.com/newticket
--John
On Wed, Mar 4, 2009 at 6:21 PM, Daniel Friesen
wrote:
>
> I just did a little check after noticing something while developing. But
> .css('margin'); and .css('padding'); are fairly
Not sure - do you have some sample markup?
--John
On Wed, Mar 4, 2009 at 2:17 PM, botskonet wrote:
>
> I've been using the following code in an app since jQuery 1.2 and it's
> been working fine. However, with an upgrade to 1.3.2 (1.3.1 worked)
> this line no longer actually performs:
>
> $('#
You should post this to the jQuery UI group.
http://groups.google.com/group/jquery-ui
--John
On Wed, Mar 4, 2009 at 4:19 AM, eamon wrote:
>
> This is working ok in ie8 but not resizing in firefox: with
> jquery-1.2.6.js and jquery-ui-personalized-1.5.3.js both ok
>
>
>
>
Thanks Marc - I'll check in to this, but it looks like a good catch.
--John
On Wed, Mar 4, 2009 at 4:26 AM, Marc Diethelm wrote:
>
> Hi
>
> Just announcing my "patch" for the bug here. I attached the diff for
> core.js to the Trac ticket. Maybe someone can review it... It's my
> first one :-P
Yep, we're planning on it! We're pulling together our list of projects
right now, in fact.
--John
On Tue, Mar 3, 2009 at 10:27 PM, hunt3131 wrote:
>
> Hey there -
>
> I was wondering if there is a plan to submit anything for jQuery to
> Google Summer of Code (http://code.google.com/soc/). I t
Hey Gavin -
Thanks for the fact-finding, that definitely clears things up - I'll
see if I can fix this for 1.3.3.
--John
On Tue, Mar 3, 2009 at 4:40 PM, d3r1v3d (Gavin Mulligan)
wrote:
>
> For kicks, I've been looking into the causes behind the problem this
> ticket poses. I've managed to du
This isn't terribly surprising. In the first case you're inserting
1000 elements, in the second case you're inserting a single element
(which so happens to have a bunch of child elements). It's always
going to be faster to insert a single element instead of 1000
elements.
--John
On Mon, Mar 2,
What I wrote in the ticket:
This is the correct behavior. If you're serving up your document as
XML you need to treat it like a proper XML document - which means only
modifying the actual DOM attributes (and not the expandos).
See here for more information:
http://docs.jquery.com/Frequently_Asked
So a quick point: What you're talking about isn't a fork, it's a
branch (you track commits in a branch, you take the project in a new
direction with a fork).
As far as your specific changes are concerned.
- I like .click(fn, fn) as an alternative to .toggle(fn, fn).
- I don't like .toggleVisibi
Also, a list of the queries that you're running would be helpful.
--John
On Tue, Mar 3, 2009 at 9:23 AM, John Resig wrote:
> What version of jQuery/Sizzle are you using? A lot of clean-up was
> done recently.
>
> Also, if you don't want the jQuery23434... prop
What version of jQuery/Sizzle are you using? A lot of clean-up was
done recently.
Also, if you don't want the jQuery23434... properties, you should use
jQuery's .html() which cleans them up.
--John
On Tue, Mar 3, 2009 at 8:22 AM, Már Örlygsson wrote:
>
> Seems like Sizzle isn't cleaning up a
You linked to some code snippets but do you have a demo page online
anywhere? And is there a bug filed related to this topic?
--John
On Mon, Mar 2, 2009 at 11:45 AM, sliver wrote:
>
> Posting a link to this thread here for possible bug in 1.3.2?
>
> http://groups.google.com/group/jquery-en/br
401 - 500 of 1010 matches
Mail list logo
