John Resig wrote:
>
> I /think/ this has to do with the fact that if you bind events inside
> of an event, in IE, then the new events will fire again too, causing
> the browser to go into a never-ending loop. You just need to be really
> careful about binding duplicate event handlers in IE (at
I /think/ this has to do with the fact that if you bind events inside
of an event, in IE, then the new events will fire again too, causing
the browser to go into a never-ending loop. You just need to be really
careful about binding duplicate event handlers in IE (at least for
now, until jQuery offe
Oh man! that makes you just another microsoft victim! Sorry!
On 10/25/06, Brice Burgess <[EMAIL PROTECTED]> wrote:
>
>
> Ⓙⓐⓚⓔ wrote:
> >
> > var embed = function(){
> > $(this).after(' — > valign="bottom"
> > height="16" width="160" src="' + this.href + '">')
>
Ⓙⓐⓚⓔ wrote:
>
> var embed = function(){
> $(this).after(' — valign="bottom"
> height="16" width="160" src="' + this.href + '">')
> .bind("click",function() {return false});
> return false;
> $("[EMAIL PROTEC
On 10/25/06, Brice Burgess <[EMAIL PROTECTED]> wrote:
>
>
> Ⓙⓐⓚⓔ wrote:
> >
> > I've accomplished rebinding simply by using oneclick(), and then in
> > the call back setting the full click(). Originally I skipped over
> > reading about oneclick, because I thought it was onclick.
> >
>
> As stated,
Franck Marcia wrote:
>
> Hi, Brice
> I ran into the same problem.
> The workaround I found was something like this:
>
>
> $(function() {
> $("#link").click(function() {
> if ($(this).html() == '') {
> alert('');
> $(this).
Ⓙⓐⓚⓔ wrote:
>
> I've accomplished rebinding simply by using oneclick(), and then in
> the call back setting the full click(). Originally I skipped over
> reading about oneclick, because I thought it was onclick.
>
As stated, oneclick() did not alleviate the issue. What version of jQ
are/were
I've accomplished rebinding simply by using oneclick(), and then in
the call back setting the full click(). Originally I skipped over
reading about oneclick, because I thought it was onclick.
On 10/25/06, Franck Marcia <[EMAIL PROTECTED]> wrote:
> 2006/10/26, Brice Burgess <[EMAIL PROTECTED]>:
>
2006/10/26, Brice Burgess <[EMAIL PROTECTED]>:
> I have a "click" event assigned to a link. When the event fires, I'd
> like to unbind this event and re-assign a new "click" event to the link.
> The re-assignment is handled within the originating "click" event.
>
> Is the a jQ bug? Is there a bette
I have a "click" event assigned to a link. When the event fires, I'd
like to unbind this event and re-assign a new "click" event to the link.
The re-assignment is handled within the originating "click" event.
This works FINE in FF 1.5/+. It crashes IE by sending it in a continuous
loop (IE seem
10 matches
Mail list logo
