CODEWITHSUNDEEP
javascriptjqueryopera
m.edmondson
m.edmondson

Reputation: 30892

Opera ignoring .live() event handler

I have the following jQuery which works in all major browsers except Opera:

jQuery(document).ready(function () {

      jQuery("#GetResults").live("click", function(e){
            e.preventDefault(); //Opera doesn't execute anything here
      });

};

Which is supposed to fire when clicking the following link:

<a id="GetResults" href="Folder/File/javascript:void(0);">Get Results</a>

Only Opera ignores this. Any ideas?

Edit:

I've just discovered that if I substitute out .live() for .bind() everything functions as expected. I can't find any documentation relating to .live() bugs in Opera though, and it does work in jsFiddle which would point at something environmental. What could be causing this behavour?

Upvotes: 8

Views: 864

Answers (7)

kleinohad
kleinohad

Reputation: 5912

Read this article. Try use delegate instead

Upvotes: 2

Nikolay Fominyh
Nikolay Fominyh

Reputation: 9256

Ensure that document.ready event happens before you click on link.

Try to put all lives in the top of the document.ready wrapper. It may help, if you have a lot of javascript code.

Upvotes: 1

jimbo
jimbo

Reputation: 11042

There are two aspects of an event bubbling worth considering in this case: propagation and the default action.

Propagation refers to the event bubbling. First the anchor tag gets the click event, then its parent element, then its parent's parent, and so forth, up to the document element. You can stop an event from propagating at any time by calling e.stopPropagation().

The default action is what the browser will do if nothing is done to prevent it. The most well-known case is when an anchor with an href is clicked, the browser will try to navigate there. There are other examples too, though, for example when you click and drag an image, many browsers will create a ghost image you can drop on another application. In both cases, you can stop the browser from doing the default action at any time by calling e.preventDefault()

As mentioned in other answers to this question, jQuery's .live() feature sets a handler at a high level element (like document) and takes action after events have propagated up. If a handler in between the anchor and the document calls e.stopPropagaiton() without calling e.preventDefault() it would stop the live handler from responding, while still allowing the browser to navigate (the default action).

I doubt this is what's happening, since it would affect all browsers, but it's one possible explanation.

Upvotes: 1

Phill
Phill

Reputation: 18794

Not sure if you want to do it, or if it will work for you. I had similar issues with Opera 9.5 and e.preventDefault() not working, the only solution I found was to just return false...

jQuery(document).ready(function () {

      jQuery("#GetResults").live("click", function(e){
            e.preventDefault();
            return false;
      });

};

Upvotes: 1

naugtur
naugtur

Reputation: 16915

This needs clarification. The answers above are correct, but nobody clearly explained where your problem comes from.

In fact I think that you could probably reproduce the problem in other browsers too. That's because of how .live works:

It binds to the event on document and waits for a particular event to bubble up to there. Then it checks if the event.target is what you wanted to handle. *

If you click on a link element it's quite possible that the browser goes to the new page before the event bubbles high enough to trigger your code. In an app with lots of HTML and event handlers all the browsers should have problems. Opera just starts displaying the new page and destroys the previous quicker in this case. It really depends on a particular situation more than on the browser. For example: you probably won't see this happen if you had a high network latency while connecting to the site.

To prevent default action on a a element you have to use .bind like in the old days ;) when a eveloper had to be aware of what he loads with AJAX and bind new events to that in a callback.

* There is more to that and .live is more complicated. I just described what is needed here.

Upvotes: 7

Дамян Станчев
Дамян Станчев

Reputation: 2664

What happens when you attach the handler using:

$ (something).bind ("click", function (e) {
    // do something
})

You can also try to attach the handler using .click() method.

Upvotes: 6

Thaddee Tyl
Thaddee Tyl

Reputation: 1214

The following code works as expected in Opera 11.50.

<!doctype html>
<title></title>
<a id="GetResults" href="http://google.com">Get Results</a>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"></script>
<script>
jQuery(document).ready(function () {
  jQuery("#GetResults").live("click", function(e){
    alert('doing something');
    e.preventDefault(); //Opera doesn't execute anything here
  });
});
</script>

Either it is a corrected bug, or something more subtle.

Can you check whether the above works on your version of Opera / jQuery?

Upvotes: 4

Related Questions