Im not sure where you see a bug of IV platform in this case, but actually you dont need to mark <iframe> tag with @unsupported
If embedded content in <iframe> is not supported in IV (like Brightcove player in this case) - IV will not be generated automatically.
P.S. First article from homepage that you provided in comment to issue #1 uses lazyload to embed images/videos - link to source is stored in data-lazy-src attribute (<iframe src="about:blank" data-lazy-src="http://path-to-embed/" />), while in current article all embeds is inserted without using lazyload (just <iframe src="http://path-to-embed/" />).
Try to use @debug: $body//iframe right after you defined body container, and in the end of all your code. If result of first and last @debug is different - that means you removed this embeds manually, and it is not a bug of IV.
thanks for the lesson . i learn the hard way . later on i think never use @unsupported ?
Type of issue
IV page is missing essential content
Reported
Feb 21, 2019
Log In
Log in here to create Instant View templates. Please enter your phone number in the international format and we will send a confirmation message to your account via Telegram.
If embedded content in <iframe> is not supported in IV (like Brightcove player in this case) - IV will not be generated automatically.
P.S. First article from homepage that you provided in comment to issue #1 uses lazyload to embed images/videos - link to source is stored in data-lazy-src attribute (<iframe src="about:blank" data-lazy-src="http://path-to-embed/" />), while in current article all embeds is inserted without using lazyload (just <iframe src="http://path-to-embed/" />).
Try to use
@debug: $body//iframe
right after you defined body container, and in the end of all your code. If result of first and last @debug is different - that means you removed this embeds manually, and it is not a bug of IV.