It has been marked as invalid and suggested to bring it up here:
http://dev.jquery.com/ticket/4946
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquer
library
> that use callbacks but wanted to go ahead and get this applied for events
> due to its popularity.
> --
> Brandon Aaron
>
> On Thu, May 7, 2009 at 12:53 PM, Balazs Endresz
> wrote:
>
>
>
>
>
> > I've just had a look at r6344 and there s
I've just had a look at r6344 and there seems to be an extra argument
in jQuery.event.add but that function hasn't been modified (yet?).
And maybe it's been mentioned before but if you're really adding this
feature why not do the same with $.each? Hopefully no one uses the
internal `args` argument
Well, if someone really needs a quick *intermediate* solution it can
be done by inserting checks with search and replace. I didn't think it
through properly at all but it seems to work if you execute these in
order (except for the loop around line 3757, where a semicolon should
be removed after `a
Have a look at these:
http://groups.google.com/group/jquery-dev/browse_thread/thread/b2f784b7575456dc/0cd276379f8a2f7d?show_docid=0cd276379f8a2f7d
On Mar 28, 1:30 am, iceman2g wrote:
> I asked this elsewhere and it was suggested that I ask here.
>
> So here goes
>
> I was curious if it's possibl
Hi, John, I'd have some similar remarks too.
Recently I've updated the patch mentioned here:
http://dev.jquery.com/ticket/3586
and spotted a couple of minor things in filter.ATTR :
(" " + value + " ").indexOf(check) >= 0 :
could be
(" " + value + " ").indexOf( " " + check + " ") >= 0 :
so the f
There is something like that but unfortunately not quite up to date:
http://demos.stuartloxton.com/downloader/
On Jan 26, 9:09 pm, Brice Burgess wrote:
> I've become accustomed to jQuery. Dependant on jQuery would be putting
> it better.
>
> As such I had the idea of building a "packager" which
Hi, there is a test case here combined with a simple solution by Mike
Alsup:
http://jquery.malsup.com/fadetest.html
On Jan 16, 11:26 pm, prefect wrote:
> Ah, yes. I came across a particularly nasty side effect with clipping
> of content with the alpha filter (I'd assume several filters do the
>
blem, then I wonder what else the
> onchange event will deal with / can. Yes I need this event.
>
> Rene
>
> Am 18. Dezember 2008 16:35 schrieb Balazs Endresz
> :
>
>
>
> > Kannst du einen Testseite zeigen? Vielleicht es gibt eine `change`
> > Event an dem
Let me put it here because this was opened a month ago, moreover it's
unassigned:
http://dev.jquery.com/ticket/3729
Now attributes seem to have some surplus of backslashes.
On Jan 15, 8:41 pm, John Resig wrote:
> > afaik: safari has are issues with case sensitivity and selectors when in
> > quir
t;
> --John
>
> On Tue, Jan 6, 2009 at 1:33 PM, Balazs Endresz
> wrote:
>
> > Regarding the other one, $('li').not(':odd:first'):
> >http://dev.jquery.com/ticket/3796
>
> > On Jan 6, 7:07 pm, "John Resig" wrote:
> >>
I tried it and the problem is exactly the same as described here:
http://dev.jquery.com/ticket/3796
On Jan 9, 10:35 am, "matas.petrikas" wrote:
> http://dev.jquery.com/ticket/3813
>
> It seems, that there's a selector regression in 1.3 beta2
>
> $('div').filter(':gt(0):lt(5)')
>
> works well in
Regarding the other one, $('li').not(':odd:first'):
http://dev.jquery.com/ticket/3796
On Jan 6, 7:07 pm, "John Resig" wrote:
> Thanks for the links guys, I've added them to my todo list.
>
> --John
>
> On Tue, Jan 6, 2009 at 12:07 PM, Balaz
Hi, here are the links correctly:
http://13beta.learningjquery.com/126.html
http://13beta.learningjquery.com/13b2.html
The last-child issue looks like easy to fix:
http://dev.jquery.com/ticket/3793
I have no idea about the other one :)
On Jan 6, 2:28 pm, Karl Swedberg wrote:
> Hi John, et. al.
There are a bunch of `nodeType === 1` checks in the selector engine, I
guess that's the cause.
OFF:
I've just noticed that there are two ` instanceof Array` checks too.
Why not use ...toString?
On Jan 5, 7:52 am, MarionNewlevant wrote:
> This html:
>
> Lorem ipsum dolor sit amet.
>
>
> Thi
a bug on them?http://dev.jquery.com/
>
> Thanks!
>
> --John
>
> On Sun, Jan 4, 2009 at 9:31 AM, Balazs Endresz
> wrote:
>
> > After some more testing there seems to be some issues with this
> > approach as it fails if you have a selector like this:
> > input[na
ithub.com/jeresig/sizzle/commit/c757d135949d0a4b15a9fd6d72907...
>
> --John
>
> On Sat, Jan 3, 2009 at 10:35 AM, Balazs Endresz
>
> wrote:
>
> > Hi,
> > a couple of months ago I made little patch to Sizzle
> >http://groups.google.com/group/jquery-dev/browse_thre
Hi,
a couple of months ago I made little patch to Sizzle
http://groups.google.com/group/jquery-dev/browse_thread/thread/d74e5a88b9649d24
to enable selection by data and css properties inside an attribute
selector:
http://jsbin.com/otoqo/edit
It uses a negative lookahead to prevent other selectors
Kannst du einen Testseite zeigen? Vielleicht es gibt eine `change`
Event an dem checkbox gebunden, dass den Verzögerung verursacht? Wenn
du $.cache löschst, dann ist es normal, dass die Events nicht
funktionieren, du sollst das nicht tun.
"$.cache ordentlich "vollläuft" - Was meinst du damit?
O
Ctrl+a -> View selection source
On nov. 24, 19:12, sarika <[EMAIL PROTECTED]> wrote:
> I have to describe a weird problem here.When a checkbox is selected, I
> make
> an AJAX call. The data retrieved from this AJAX call is rendered in 2
> dropdowns within a div. On a successful AJAX callback, I c
Here's another version that supports data and css too:
http://jsbin.com/otoqo/edit
$('*[~display=block]') //~ for css
$('*[:foo.bar=1234]') //: for data
On Nov 2, 10:13 pm, Ariel Flesler <[EMAIL PROTECTED]> wrote:
> Seems fine to me. The ideal place for it would be inside $.expr[':']
> but I'm
I think the attribute syntax feels natural because it compares values
too. Anyway, you still have to do something with the dots
inside :data(foo.bar), now it doesn't accept them. In Sizzle the dots
only collide with the class filter, but I don't know why it doesn't
work in jQuery.
On Nov 3, 6:26
I've just made a small patch to Sizzle: http://jsbin.com/omipi/edit
It works like: Sizzle("div[data.foo.bar^=12]");
I first thought of using ":" too in the square brackets but i fear
that needs a bit more hacking with other regular expressions too, but
that would work better for sure.
Just for the
What do you think about chaining this way:
jQuery.callback = function(){
var args = jQuery.makeArray(arguments);
if(typeof args[0] == 'string' )
args=[args];
return function(){
for(var i in args){
fn = args[i].shift();
jQuery.fn[ fn ].apply( jQuery(this), args[i] );
that
replaces the content from this direction.
I like this but I'm not fully convinced either, just an idea :)
On Oct 1, 2:52 am, "Jaime Ochoa Malagón" <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 3:20 PM, Balazs Endresz
>
> <[EMAIL PROTECTED]>
Someone came up with this recently:
"Now, of course I can do this:
$("#sandbox").text( $("a").text() );
But I'd prefer to do this:
$("a").text().appendTo("#sanbox"); "
http://groups.google.com/group/jquery-en/browse_thread/thread/bbd886b73e7768e1
I also think that this way would be a bit eas
26 matches
Mail list logo
