Wed, Jan 13, 2010 at 3:39 AM, helianthus
>
> wrote:
> > I see no fix on this bug in v1.4rc1??
>
> Did you file a bug report athttp://dev.jquery.com/?
>
> -- Scott
--
You received this message because you are subscribed to the Google Groups
"jQuery Development&quo
I see no fix on this bug in v1.4rc1??
--
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.
http://github.com/jquery/jquery/blob/master/src/event.js#L401
I did not know that there has been normalization for event.which until
looking up the new API browser today.
I could (partly) understand the choice of using event.which for
keyboard event, since it is a mess and there is no standard for
ydown click' and see if the problem
> goes away.
>
> Also, try it again with jQuery 1.3.2 and see if it behaves the same way. If
> not, it is a regression that somebody needs to look at.
>
> -- John
>
> On Sat, Jan 9, 2010 at 6:46 PM, helianthus
> wrote:
>
still think you have not provided
> enough information to understand what the problem is.
>
> Let's see some sample code. A test page that shows the problem.
>
> On Sat, Jan 9, 2010 at 12:39 AM, helianthus
> wrote:
>
>
>
>
>
> > jQuery.event.special.cl
7;anothertype,' it will not find a special handler for 'anothertype' and so
> it will do the 'normal' thing of adding an event listener to the element.
>
> Your question implies that you expect it not to. Why would you expect it
> not to add an event listener
Arrowwood wrote:
> Your question is not clear. When you do .bind('event1 event2',fn) you add
> an event handler for both events. This is to be expected. So why would you
> think that the code below would not modify the 'anothertype' event?
>
> On Fri, Jan 8, 20
For example,
if I had created a special add handler for click event,
when I do something like jQuery.bind('click anothertype', function()
{...}),
the handler of anothertype is also modified.
If the above is not clear enough I can write a test case.
--
You received this message because you are sub
post-1.4.
>
> --John
>
> On Mon, Dec 21, 2009 at 1:42 PM, helianthus
>
>
>
> wrote:
> > Here is the test case:http://jsbin.com/akaza/edit
>
> > I have simply tested on IE8, Chrome 4, Opera 10 and FF 3.5,
> > and found out that only FF 3.5 successfully has
Here is the test case: http://jsbin.com/akaza/edit
I have simply tested on IE8, Chrome 4, Opera 10 and FF 3.5,
and found out that only FF 3.5 successfully has the event prevented.
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to
/jquery/commit/9a0174b057ae58735c3c5f595e420c...
>
> --John
>
> On Wed, Dec 16, 2009 at 11:02 PM, helianthus
>
>
>
> wrote:
> > But my code broke after switching from 1.4a1 to 1.4a2...
> > and removing that check fixed it.
> > I guess I have to check again what b
mptied (the logic hasn't changed from when
> the ready method was in event.js).
>
> --John
>
> On Wed, Dec 16, 2009 at 9:06 PM, helianthus
>
>
>
> wrote:
> > At line 223 of core.js,
> > readyList is an array, which will never be falsy,
> > so the b
At line 223 of core.js,
readyList is an array, which will never be falsy,
so the block will never be executed.
--
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
This occurs when using jQuery.fn.index, which utilizes jQuery.inArray.
Since the jQuery object does not have an indexOf method, it falls back
to the for loop approach, while Array.prototype.indexOf could have
been used.
--
You received this message because you are subscribed to the Google Groups
i guess i just found a bug?
At line 3961, the filter variable is not declared properly.
After adding back a "var" at the beginning, the error in my app is
gone.
(Strangely, at the same line no semicolon at the end?)
On Dec 5, 4:44 am, John Resig wrote:
> More details
> here:http://blog.jquery.c
On 4月5日, 上午11時41分, helianthus wrote:
> Hey I found out where it goes wrong.
> It is at line 3177 of jquery-1.3.2.js, where the following code is
> written:
>
> root.insertBefore( script, root.firstChild );
>
> After commenting it out, the page loads without problems.
>
Hey I found out where it goes wrong.
It is at line 3177 of jquery-1.3.2.js, where the following code is
written:
root.insertBefore( script, root.firstChild );
After commenting it out, the page loads without problems.
John, is it enough info for you fix it?
--~--~-~--~~~--
I remembered this article I read quite a long time ago:
http://blog.stevenlevithan.com/archives/faster-trim-javascript
On 1月31日, 上午5時02分, dimi wrote:
> Hi folks,
>
> I have a large HTML fragment that I load via AJAX. The fragment is big
> (~660KB),
> and it takes over 2s (more like 2.7s) to inse
ng or analyzing Opera
> userjs.
>
> --John
>
> On Wed, Jan 28, 2009 at 5:05 PM, helianthus
>
>
>
> wrote:
>
> > just tried the lastest nightly build, still got no luck...
>
> > On 1月28日, 上午3時09分, helianthus wrote:
> >> Tried that, same result..
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 Zhou wrote:
>
>
>
> > What happens if you use the full un-minified version?
> > -- dz
>
> > On T
Tried that, same result...
On 1月28日, 上午3時07分, David Zhou wrote:
> 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,
ges?) would be useful.
>
> --John
>
> On Tue, Jan 27, 2009 at 10:41 AM, helianthus
>
>
>
> wrote:
>
> > Got no replies at the General Discussion so I'm posting here:
>
> > I have been writing a user-script(userjs) with jQuery recently, the
> > way
nt it).
>
> --Fabio
>
>
>
> On Tue, Jan 27, 2009 at 5:48 PM, David Zhou wrote:
>
> > 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:
>
Got no replies at the General Discussion so I'm posting here:
I have been writing a user-script(userjs) with jQuery recently, the
way I integrate jQuery is to copy the minified code into the user-
script.
It had been working fine until I updated jQuery to 1.3, while on
other
browsers(FF3, Chrome,
can anyone confirm??
On 1月24日, 上午3時01分, helianthus wrote:
> 1.2.6:
> No problems on all browsers tested.
> 1.3.1:
> IE7 & IE8 beta2: Fires only after all images are completely loaded.
> FF3, Opera 9, Chrome: Fires right
1.2.6:
No problems on all browsers tested.
1.3.1:
IE7 & IE8 beta2: Fires only after all images are completely loaded.
FF3, Opera 9, Chrome: Fires right after DOM is loaded.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
26 matches
Mail list logo
