For IE, isObject(), is perhaps not that trivial ... DBJ
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...
oops: "evaluated without context"
On Nov 8, 12:48 am, Robert Katić wrote:
> I detect only now that in closest method the selector is evaluated
> without selector.
> I am not sure which context is more correct: (context || this.context)
> or it have to be a document?
>
> PS: It is not completely c
I detect only now that in closest method the selector is evaluated
without selector.
I am not sure which context is more correct: (context || this.context)
or it have to be a document?
PS: It is not completely clear to me why selectors with positions can
not be handled by multiFilter in this situa
Uhmm, nevermind.
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, vi
Imagine I have a form that contains this:
The following query returns "1" as expected:
$($('input[class="myclass"]')[0]).attr('value')
But if you surround the "1" value in brackets like so:
The same query returns the empty string. All the other attributes of
the input work fine
I've already landed the commits - looks great - thanks! (I'll close
the ticket once my network stops flaking out.)
--John
On Sat, Nov 7, 2009 at 5:47 PM, Robert Katić wrote:
> I opened a ticket: http://dev.jquery.com/ticket/5470
> with link on commit.
>
> Commit also includes context inside li
I opened a ticket: http://dev.jquery.com/ticket/5470
with link on commit.
Commit also includes context inside liveHandler (it is a too small
change to make a separate commit).
Component is "unfiled". Please tell me if I made mistakes opening this
ticket.
On Nov 6, 3:01 pm, John Resig wrote:
> >
Also, landing the change will fix this bug:
http://dev.jquery.com/ticket/3861
(where right and middle clicks also show up in live)
--John
On Sat, Nov 7, 2009 at 5:14 PM, John Resig wrote:
> This has been discussed before but I was just curious if this would
> affect anyone negatively. I'd lik
This has been discussed before but I was just curious if this would
affect anyone negatively. I'd like to make this change so that less
bubbling has to occur (both documentElement and document no longer
have to get hit).
Roughly, the line in the .live implementation would end up being changed from
Ah, great - thanks for the clarification and patch!
--John
On Sat, Nov 7, 2009 at 7:26 AM, Mr Speaker wrote:
> After some more testing I realised it was not so serious - it only
> occurred when 404ing from the local filesystem. This doesn't actually
> generate a 404, but an NS_ERROR_DOM_BAD_UR
To handle click delegation I took the approach of enhancing the click
event using the special events framework. This might be a slight
tangent to this thread, but it does address many of the problems
discussed here. Here's the code:
http://webdev.stephband.info/events/click/js/jquery.event.click
Great news!
On Nov 7, 6:43 am, John Resig wrote:
> Thanks for the kind words, Chris, I appreciate it! I'm slowly getting
> more organized (figuring out where we stand and what bugs we're
> missing) - I hope to push out a really solid release.
>
> I almost have the new bug tracking system set up (
12 matches
Mail list logo
