Databases
StackOverflow2013
Postsdbo
POWhy cant a mouseup event prevent a click event
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy cant a mouseup event prevent a click event
    primarykey
    data
    text
    <p><a href="http://jsfiddle.net/zhAHt/1/" rel="noreferrer">jsfiddle</a></p> <pre><code>&lt;div class='wrapper'&gt; &lt;button class='child'&gt;Click me&lt;/button&gt; &lt;/div&gt; function h(e) { e.preventDefault(); e.stopPropagation(); e.stopImmediatePropagation(); alert(e.type); return false; } document.querySelector('.wrapper').addEventListener('mouseup', h, false); document.querySelector('.child').addEventListener('click', h, false); </code></pre> <p>I expect this to prevent the 'click' event from firing, but it doesn't. However, changing <code>mouseup</code> to <code>mousedown</code> does in fact prevent the click event.</p> <p>I've also tried setting the <code>useCapture</code> argument to true, and that also doesn't produce the desired behavior with <code>mouseup</code>. I've tested this on Chrome and Firefox. Before I file bugs, I figured I'd ask here.</p> <p>Is this a bug in current browsers, or is it documented behavior?</p> <p>I've reviewed the <a href="http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-flow" rel="noreferrer">W3C standard (DOM level 2)</a>, and I wasn't able to find anything that could explain this behavior, but I could have missed something.</p> <p>In my particular case, I'm trying to decouple two pieces of code that listen to events on the same element, and I figured using capture events on the part that has priority would be the most elegant way to solve this, but then I ran into this problem. FWIW, I only have to support officially supported versions of FF and Chrome (includes ESR for FF).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAndreas Köberle
    1. UStjameson
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy cant a mouseup event prevent a click event
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy cant a mouseup event prevent a click event
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`preventDefault` and `stopImmediatePropagation` are unnecessary here (by the way), because there's no `<form>` so no submitting with the button, and no multiple events of the same type. And I *think* this is expected behavior because doesn't `mouseup` fire before `click`? So the `.child`'s `mouseup` event fires (and bubbles) before its `click` event (which you have stopped, but it doesn't matter)
      singulars
      1. POWhy cant a mouseup event prevent a click event
      1. USIan
    2. CO@Ian - I added those in to make sure I didn't get comments like "have you tried x() or y()?". For your other comment, setting `useCapture` to true forces `.wrapper`'s mouseup to happen before the bubble from child. I didn't include this code, because in either case, I should only get one alert() (with a different originating element), right?
      singulars
      1. POWhy cant a mouseup event prevent a click event
      1. UStjameson
    3. COIf you want to prevent a mouseclick, use this: http://jsfiddle.net/zhAHt/9/
      singulars
      1. POWhy cant a mouseup event prevent a click event
      1. USuSeRnAmEhAhAhAhAhA
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload