On Fri, Jul 8, 2011 at 5:21 AM, Sean Hogan <shogu...@westnet.com.au> wrote: > On 8/07/11 8:28 AM, Jonas Sicking wrote: >> >> On Thu, Jul 7, 2011 at 3:21 PM, John J Barton >> <johnjbar...@johnjbarton.com> wrote: >>> >>> Jonas Sicking wrote: >>>> >>>> We are definitely >>>> short on use cases for mutation events in general which is a problem. >>>> >>> 3. Client side dynamic translation. Intercept mutations and replace or >>> extend them. This could be for user tools like scriptish or stylish, dev >>> tools to inject marks or code, or for re-engineering complex sites for >>> newer >>> browser features. >> >> I don't fully understand this. Can you give more concrete examples? > > - MathJax (http://mathjax.org) is a JS lib that facilitates putting math > onto the web by converting LaTeX or MathML markup in a page to HTML. By > default MathJax triggers off the onload event to run this conversion on the > page. When content containing math is dynamically added to the page, MathJax > must be called manually to convert the new content. A DOM insertion listener > could potentially be used to handle this conversion automatically. > > - A similar use-case is element augmentation too complex for CSS :before and > :after > > - ARIA support in JS libs currently involves updating aria-attributes to be > appropriate to behavior the lib is implementing. Attribute mutation > listeners would allow an inverse approach - behaviors being triggered off > changes to aria-attributes. > > - DOM insertion and removal listeners could facilitate the implementation of > automatically updating Table-of-* (Headings / Images / etc).
Do any of these require synchronous callbacks? Do any of these use mutation events today? / Jonas