Interval mechanism is active despite being run in newest Chrome where mutationObserver is supported

Running the example in Chrome with the console visible I can see the Log output. No interval mechanism is active there.

But when I run my own tryout page I can see in the console that the script is always busy, always writing to the console. So I assume the interval mechanism is active. But how is that possible? My browser is the newest Chrome and supports mutationObserver.

Edit: I just noticed, the iframe content seems to always grow, not fast, but it steadily grows larger.

I use “iframe-resizer”: “^4.2.11”

The relevant parts in my setup are:

    <style>iframe{width:100%}</style>

    <iframe
      data-iframe
      src="https://canadalife-info.de/-lp/t9w5k12755/6ZZSl5"
      id="iFrameResizer1"
      scrolling="no">
    </iframe>

import { iframeResizer } from 'iframe-resizer';
const init = (iframe) => {
  iframeResizer(
    {
      checkOrigin: false,
      log: true,
      heightCalculationMethod: 'max',
    },
    iframe,
  );
};

Google Chrome ist auf dem neuesten Stand. Version 84.0.4147.135 (Offizieller Build) (64-Bit)

[teetotum]

Sorry for spamming. I just discovered that the iframe content uses setInterval(some_func, 1000) in an inline script to update the value of a hidden input field, incrementing it each second by 17 (WTF?). Am I right when I assume this is a DOM change, thereby triggering the mutationObserver, thereby triggering the re-evaluation of the whole iframe-resizer size-checking mechanism, thereby printing the corresponding log output to the browser console. And this means that I was wrong in thinking that the interval mechanism was kicking in. And the content is not growing, it just never shrinks, which means when I resize the browser a few times like a madman it gets stuck in the biggest height, not shrinking back to normal size, and I therefore thought it must be growing over time ( Just me jumping to conclusion once again.) Call me Sherlock.

Solved. There was a CSS rule in the content html,body { height: 100%; }. After I removed it the content resized as intended.

[davidjbradshaw]

Yep that sums it up.

On Wed, 26 Aug 2020 at 15:02, Martin [e-mail] wrote:

Sorry for spamming. I just discovered that the iframe content uses setInterval(some_func, 1000) in an inline script to update the value of a hidden input field, incrementing it each second by 17 (WTF?). Am I right when I assume this is a DOM change, thereby triggering the mutationObserver, thereby triggering the re-evaluation of the whole iframe-resizer size-checking mechanism, thereby printing the corresponding log output to the browser console. And this means that I was wrong in thinking that the interval mechanism was kicking in.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/davidjbradshaw/iframe-resizer/issues/851#issuecomment-680898990, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEQOEQROHZVJY2H2XLBQULSCUIW7ANCNFSM4QKRKTJQ .

– Sent from my iPhone.