As it stands we don't provide an explicit way to remove .hover() events.
They can be removed using .unbind(mouseenter/mouseleave) - which is what
would need to happen here, as well.
It's a good point - but I'm not hugely concerned.
--John
On Sat, Jul 18, 2009 at 7:42 PM, Már
Andrew -
We've thought about this issue a bunch and, unfortunately, there's just not
a whole lot that can be successfully removed from jQuery.
For example, if we scale back to just using querySelectorAll then all
filter() operations will fail (since qSA doesn't provide a means of
filtering, only
This may possibly be a jQuery UI issue, you should post your question to the
jQuery UI list:
http://groups.google.com/group/jquery-ui
--John
On Fri, Jul 17, 2009 at 11:07 AM, vrn_shan varun.c...@gmail.com wrote:
We are using jQuery 1.3.2 and jQuery UI 1.7.2 in our project.
Everything was
A couple quick points -
First, it seems like you're using the namespaces backwards. Normally you
would do 'init.collapsable', 'expand.collapsable', etc. (thus you would be
able to remove all the init events in the collapsable namespace, for
example).
If you could make a demo page demonstrating
Hmm - which nightly are you running? That change appears in the source for
me.
http://code.jquery.com/jquery-nightly.js
--John
On Wed, Jul 15, 2009 at 9:31 PM, jnunemaker nunema...@gmail.com wrote:
Ticket #4532 (Live event handlers don't receive custom event data) is
closed but I just
.
document = window.document,
is that OK?
On Wed, Jul 15, 2009 at 12:28 AM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
Not now (I am with an USB pen without bandwidth allowed) ... I'll try
tomorrow during lunch break.
Cheers
On Wed, Jul 15, 2009 at 12:19 AM, John Resig jere
?
On Wed, Jul 15, 2009 at 12:28 AM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
Not now (I am with an USB pen without bandwidth allowed) ... I'll try
tomorrow during lunch break.
Cheers
On Wed, Jul 15, 2009 at 12:19 AM, John Resig jere...@gmail.com wrote:
Cool - could you file a bug
Why not make sure that the e.target is equal to the active element before
re-firing the event?
if ( e.target === this ) {
// your code
}
--John
On Wed, Jul 15, 2009 at 3:39 PM, Jeffrey Kretz jeffkr...@hotmail.comwrote:
I hate to bump this, but I haven't yet been able to figure out a
Pete -
Does it work with the jQuery nightlies? We made some tweaks to how
:hidden/:visible worked in 1.3 and have since made some more changes to
hopefully fix bugs.
http://code.jquery.com/jquery-nightly.js
--John
On Wed, Jul 15, 2009 at 3:28 PM, Pete Schwamb pschw...@gmail.com wrote:
I
As we discussed on IM, the parent.document || part would be untennable
(since it would make all iframed copies of jQuery incapable of operating
within the frame itself).
Would the resulting change,
(function(document){
})(document);
be acceptable?
--John
On Tue, Jul 14, 2009 at 11:32 AM,
So I refused to believe that such a massive bug actually existed. I did some
digging and built a test case:
http://ejohn.org/files/bugs/modified/
http://ejohn.org/files/bugs/modified/headers.phps
Sure enough, there's a complete failure.
Opera = 9.6 are incapable of doing
I've committed the changes that I mentioned, here:
http://dev.jquery.com/changeset/6432
The test suite is now passing in all browsers (save Opera 10b1, which has
issues with :enabled/:disabled).
--John
On Tue, Jul 14, 2009 at 5:00 PM, John Resig jere...@gmail.com wrote:
So I refused
Well, you could also do:
$(h1).prepend(§);
The reasoning behind handling selectors (and HTML) in $(...) and then later
appending/prepending/etc. them into the document is that you can modify them
in the interim.
For example:
$(h1Something/h1).click(function(){ }).prependTo(div.section);
So I guess you're saying that there shouldn't be a need to work with
text nodes, so no shortcut is necessary. Fair enough.
Yeah, I'm open if some interesting use cases are proposed but for now I'm
hesitant to add new syntax/parsing to $(...) for minor benefit.
--John
... too easy!
Best Regards
On Jul 14, 2009 8:36 PM, John Resig jere...@gmail.com wrote:
As we discussed on IM, the parent.document || part would be untennable
(since it would make all iframed copies of jQuery incapable of operating
within the frame itself).
Would the resulting change
Filed and fixed:
http://dev.jquery.com/ticket/4902
http://dev.jquery.com/changeset/6434
--John
On Tue, Jul 14, 2009 at 7:01 PM, David Flanagan da...@davidflanagan.comwrote:
If the argument to a wrap function is a string that contains text, it
doesn't do what I'd expect it to.
For example:
This one was tricky because we've never explicitly said *not* to use
multiple elements in wrap, just that you should have one. There were two
options:
- Ignore the remaining elements (as you suggested) and possibly break some
unknown code.
- Create a new case where .pushStack is used,
We already attempt to do this, internally, If we encounter an element that
we need to show we create a temporary one and figure out the display type of
that element (and use that, instead).
It should be noted that animating the height or width of a table, in
general, is a bad idea (they behave
Good catch - and thanks for the patch! I just landed the improvement:
http://dev.jquery.com/ticket/4884
I made one minor tweak to the patch: In the case where .attr(name,
function(){}) occurs the jQuery.isFunction(value) check is cached (rather
than occurring at every iteration in the array).
Re-wording the documentation from 'deprecated' to 'strongly discourage
the use of' (or something similar) might be ok. I'm not sure what else
we can do on our end - we already link to a number of guides that
provide good information on the subject matter.
As to the linked Stack Overflow
Good call, fixed.
--John
On Sun, Jul 5, 2009 at 1:32 PM, Gregorgregor.tram...@gmail.com wrote:
I would like to point out a documentation error on wiki page:
http://docs.jquery.com/Utilities/jQuery.grep#arraycallbackinvert
The Order of arguments in the argument section is switched:
All of these points sounds very reasonable to me. Making these changes
to the markup will require some changes to our tests (since some IDs
are referenced by name) but this is a change that would be acceptable
to make.
Looking forward to your patch!
--John
On Thu, Jul 2, 2009 at 1:55 PM,
Yeah, this was intentional - since Safari now has a decent DOM ready
technique, we switched to that. To be clear: It's not possible to run
the ready event if jQuery is dynamically loaded in any browser that
uses .addEventListener( DOMContentLoaded ... ).
Well, at least, can't detect it using
A patch that implements something like this would be considered seriously.
--John
On Tue, Jun 30, 2009 at 6:05 AM, Ricardoricardob...@gmail.com wrote:
onerror seems to only work in Firefox. I can only see this implement
for JSONP with a timeout that removes/empties the callback, it's
Mike -
I'm unfamiliar with this particular situation - if you're able to,
somehow, duplicate it for us that would be very helpful.
--John
On Tue, Jun 30, 2009 at 7:40 PM, Mike Galei...@decisionz.com wrote:
I have a web site that uses jQuery to populate and manipulate drop
down lists
Well - if there was any progress it would probably be mentioned in the
ticket itself.
It doesn't seem like that wouldn't be too hard to fix, I'll look in to it.
--John
On Thu, Jun 25, 2009 at 9:01 AM, Hakdjcapet...@gmail.com wrote:
Hi, has there been any developments to the following bug:
You can see the default implementation here:
http://dev.jquery.com/browser/trunk/jquery/src/ajax.js#L158
--John
On Thu, Jun 25, 2009 at 2:29 PM, Etienne
Robillardrobillard.etie...@gmail.com wrote:
Hi flesler,
Well if you do provide a fallback then please show me the relevant
part in the
$.ajaxSettings in
1.3.2 ?
Best regards,
Etienne
John Resig wrote:
You can see the default implementation here:
http://dev.jquery.com/browser/trunk/jquery/src/ajax.js#L158
--John
On Thu, Jun 25, 2009 at 2:29 PM, Etienne
Robillardrobillard.etie...@gmail.com wrote:
Hi flesler,
Well
Hmm, I hadn't realized that the bug had been re-opened. It looks like
there's another related issue at play. Added to my todo list.
--John
On Thu, Jun 25, 2009 at 6:18 PM, JohnnyCeejfcardi...@gmail.com wrote:
I recently updated my product to use jQuery 1.3.2 and I gave beta
testers a
be something simple like checking if it starts with and
ends with , contains no other 's and doesn't have a / before the
then insert a single / before the last before continuing.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
John Resig wrote:
Unfortunately
Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
John Resig wrote:
I'm hesitant to support that since it tends to promote passing in
malformed (X)HTML. At least with span attr='val'/ it's obvious that
it should be a standalone.
--John
On Tue, Jun 23, 2009 at 12:27 AM, Daniel
Yeah, I think all outstanding bugs with that were fixed in 1.3.0.
--John
On Tue, Jun 23, 2009 at 2:56 PM, Kelvin Luckkel...@kelvinluck.com wrote:
On Tue, 23 Jun 2009 12:40:11 -0400, John Resig jere...@gmail.com wrote:
To be clear: jQuery supports the pattern, it just requires the closing
of a single tag
as malformed html.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
John Resig wrote:
To be clear: jQuery supports the pattern, it just requires the closing /.
$(td/) // ok
$(td) // ambiguous, malformed, not ok
$(a href='http://google.com/'/) // ok
More information about this style of attributes can be found here:
http://ejohn.org/blog/html-5-data-attributes/
Great work Yehuda!
--John
On Tue, Jun 23, 2009 at 3:31 PM, Yehuda Katzwyc...@gmail.com wrote:
I just released jQuery Metadata 2.1, which adds support for HTML5 data-*.
Usage:
p
You say that you still have problems if you split apart the query.
So in this case $button.append( [ ) fails - correct?
What happens if you do:
$button.append( document.createTextNode([) )
--John
On Mon, Jun 22, 2009 at 2:09 PM, Daniel
Friesennadir.seen.f...@gmail.com wrote:
I've been
That's definitely an odd one. Thanks for putting it on my radar, at
least. I have it on my todo list and when some time frees up I'll try
and poke at it to see what can be done.
--John
On Mon, Jun 22, 2009 at 2:48 PM, Usmanus...@loudwaterlabs.com wrote:
I'm using jQuery 1.3.2 with JBoss
-Seen-Fire) [http://daniel.friesen.name]
John Resig wrote:
You say that you still have problems if you split apart the query.
So in this case $button.append( [ ) fails - correct?
What happens if you do:
$button.append( document.createTextNode([) )
--John
On Mon, Jun 22, 2009 at 2:09 PM
Unfortunately jQuery selectors are not supported on Document
Fragments. Fragments are quite feature-poor and don't even provide
basic DOM-querying functionality in some browsers. For example the
following will return undefined in Firefox 3:
Interesting fix, Rich. I've CC'd in Diego who's been doing a lot of
work with the ready code lately.
--John
On Mon, Jun 22, 2009 at 5:53 PM, Rich Doughertyr...@rd.gen.nz wrote:
On Feb 7, 11:55 am, Paul Irish paul.ir...@gmail.com wrote:
I can report that the jquery-2009-01-28.js nightly,
Hmm, I don't think we're planning on having another update to the
1.2.x branch at this point - but thanks for the heads-up.
--John
On Fri, Jun 19, 2009 at 5:47 AM, tarinitarin...@gmail.com wrote:
I found a bug on jQuery 1.2.6 that has been fixed on 1.3.*
It's about using plus in selector
What happens if you try:
jQuery('a:not([href*=#][href*=javascript]')
also - do you have a sample demo page that we can look at? Thanks!
--John
On Thu, Jun 18, 2009 at 7:55 AM, pbcommpbc...@gmail.com wrote:
James,
I'm looking for the links that do NOT start with '#' or 'javascript',
and
/livenot.html
On Jun 18, 8:23 am, John Resig jere...@gmail.com wrote:
What happens if you try:
jQuery('a:not([href*=#][href*=javascript]')
also - do you have a sample demo page that we can look at? Thanks!
--John
On Thu, Jun 18, 2009 at 7:55 AM, pbcommpbc...@gmail.com wrote:
James,
I'm
-Fire) [http://daniel.friesen.name]
John Resig wrote:
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
).someOtherFnMethod();
been fixed?
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
John Resig wrote:
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
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 any
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
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
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
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, rimmer333e.efimoch...@gmail.com wrote:
Hello.
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
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 wyc...@gmail.com wrote:
I'd like to submit a patch that lets all setters (val, html, text, etc.)
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
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 e.ma...@gmail.com wrote:
Hi,
I have recently upgraded from jQuery 1.2 to the current
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 alex.far...@gmail.com wrote:
I noticed val() ignores the 'value' attribute on html elements.
If i have this markup:
div
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
What would these properties be used for?
--John
On Fri, May 22, 2009 at 5:21 PM, Ralf Stoltze
ralf.stol...@googlemail.comwrote:
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
]
*On Behalf Of *John Resig
*Sent:* Tuesday, May 19, 2009 4:20 PM
*To:* jquery-dev@googlegroups.com
*Subject:* [jquery-dev] Re: window['eval']() in rhino
I don't remember the original discussion/change, off-hand. If YUIMin is
still able to generate
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 jere...@gmail.com wrote:
Ok, it all sounds in order to me - someone want to file a ticket?
http://dev.jquery.com/newticket
--John
On Wed
(whatever)();
On Wed, May 20, 2009 at 10:29 PM, John Resig jere...@gmail.com wrote:
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 jere...@gmail.com wrote:
Ok, it all sounds in order to me
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.tumblr.com/
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 justinbme...@gmail.comwrote:
I assume there must be a good
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 brandon.aa...@gmail.comwrote:
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 papp...@gmail.comwrote:
(Solution found... more info provided
To be clear - Firefox is returning an object/ element - the bug is that
doing typeof on an object/ 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
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
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 jeffery...@gmail.com 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
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ć robert.ka...@gmail.com wrote:
After some readings on the A Modest Proposal: jQuery Enterprise
discussion at
...@kelvinluck.com wrote:
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 jere
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 kel...@kelvinluck.com
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 jack.ba...@gmail.com wrote:
How can I do an AJAX request with jQuery and *not* add the X-Requested-
With header?
I am
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 miqu...@gmail.com wrote:
I am after a way to better integrate Qunit into a continuous
integration system. I need quinit
This should go in a new thread.
--John
On Fri, Apr 24, 2009 at 4:54 PM, Michael Park emp...@gmail.com 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
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
Actually, r6310:
http://dev.jquery.com/changeset/6310
Thanks Brandon.
--John
On Tue, Apr 21, 2009 at 2:53 PM, Brandon Aaron brandon.aa...@gmail.com 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
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+xml
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 rmurp...@gmail.com wrote:
The issue didn't occur in IE; I haven't tested in C or S.
As
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
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
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
b...@grandcentralapartments.com wrote:
On Apr 13, 8:34 am, Leonardo K leo...@gmail.com wrote:
*From jQuery site:
Note:* In jQuery 1.3 [...@attr] style selectors were
Julián
On Apr 5, 12:43 am, John Resig jere...@gmail.com wrote:
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 mani...@gmail.com
wrote:
Hi again
Which aspect? Do you have a demo?
--John
On Fri, Apr 3, 2009 at 2:46 PM, sfearl1 sfea...@gmail.com wrote:
this has still not been fixed
On Mar 3, 9:34 am, Már Örlygsson mar.orlygs...@gmail.com wrote:
What version of jQuery/Sizzle are you using? A lot of clean-up was
done recently.
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
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
.
--John
On Tue, Mar 31, 2009 at 10:28 AM, Jakub Suder jakub.su...@gmail.com wrote:
On 31 Mar, 15:40, John Resig jere...@gmail.com 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.js
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 yodza...@gmail.com wrote:
Hi,
From 1.3.1 to 1.3.2 sibling selector does not work anymore:
If I'm understanding the problem correctly, you'll want this:
$(.gallery img).clone().appendTo(#bild_spel div ul).wrap(li/li);
(remove the .clone() if you want to move the img elements, as well)
--John
On Mon, Mar 30, 2009 at 6:48 AM, smurkas marcus.dalg...@gmail.com wrote:
Hello.
I
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
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
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 the
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
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 since
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:
);
throw e;
}
}
var handlers = [
function(){
throw A;
},
function(){
throw B;
}
];
This one will throw both (all) errors.
Am I missing something?
On Mar 24, 10:13 pm, John Resig jere...@gmail.com wrote:
I don't think it is the resposibility of the dispatcher to handle
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
nadir.seen.f...@gmail.comwrote:
At work I tried to animate something to grow horizontally then grow
vertically.
Probably, yeah - could you file a ticket?
--John
On Sat, Mar 21, 2009 at 1:57 PM, David Citron dcit...@gmail.com 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.
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
nadir.seen.f...@gmail.comwrote:
Originally the lead programmer wanted to avoid making the core
) (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 height determined if you've already explicitly
overwritten
.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_Events
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:
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 pdoddam...@gmail.com wrote:
Hi
table cellspacing=0
301 - 400 of 748 matches
Mail list logo
