Databases
StackOverflow2013
Postsdbo
POWatching for DOM changes, the elegant way
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWatching for DOM changes, the elegant way
    primarykey
    data
    text
    <p>I need to watch for an attribute change on any of the children of a specific DOM element. So far, I have been using <a href="https://developer.mozilla.org/en/DOM/Mutation_events" rel="noreferrer">mutation events</a>.</p> <p>The problem was - they were buggy: e.g. under Chromium, <code>DOMAttrModified</code> was not fired but <code>DOMSubtreeModified</code> was. The problem was easy to solve: because according to the specification, <code>DOMSubtreeModified</code> is fired if any of the other events is fired, so I just listened to <code>DOMSubtreeModified</code>.</p> <p>Anyway, Chromium, in the recent versions, stopped firing anything if an attribute has been modified. </p> <p>The new <a href="http://updates.html5rocks.com/2012/02/Detect-DOM-changes-with-Mutation-Observers" rel="noreferrer">Mutation Observer API</a>, however, works flawlessly.</p> <p>Until now, I only need to fire a callback upon ANY change of the subtree of a specific element - simply because nothing else is supposed to change - so I solved my problem by just using mutation events &amp; mutation observer (when available) in the same piece of code.</p> <p>However, now I need to do more powerful filtering of the events (e.g. on new node, on removed node) - so is there <strong>a library, possibly a jQuery plug-in</strong>, that would allow me to elegantly use <strong>both</strong> of these APIs - <code>MutationObserver</code> if available and mutation events as a fallback, with the ability to filter for specific event types (e.g. element added, attribute changed).</p> <p>E.g. </p> <pre><code>$("#test").watch({onNewElement: 1}, function(newElement){}) $("#test").watch({onNewAttribute: 1}, function(modifiedElement) {}) </code></pre> <p>Or without jQuery</p> <pre><code>watchChanges("#test", {onNewElement: 1}, function(newElement){}) watchChanges("#test", {onNewAttribute: 1}, function(modifiedElement){}) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPraveen Kumar Purushothaman
    1. USIvo
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWatching for DOM changes, the elegant way
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWatching for DOM changes, the elegant way
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWatching for DOM changes, the elegant way
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSome searching found this, but it only supports the new API: http://code.google.com/p/mutation-summary/. I also found this, which appears to be a simple version of what you're asking for: http://stackoverflow.com/questions/10868104/can-you-have-a-javascript-hook-trigger-after-a-dom-elements-style-object-change
      singulars
      1. POWatching for DOM changes, the elegant way
      1. USthirtydot
    2. COI also found mutation-summary, but it does not support mutation events as a fallback. The first answer of the thread you posted is basically what I do in my code to observe attribute changes. In the same principle, a library can be built that allows watching for specific DOM events using both mutation observers and (as a fallback) events. That is what I need.
      singulars
      1. POWatching for DOM changes, the elegant way
      1. USIvo
    3. CO+1: I really dig 'best practice' questions.
      singulars
      1. POWatching for DOM changes, the elegant way
      1. USJezen Thomas
 

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