The processing model only works for iframes, not object/embed/etc.

[domenic]

The processing model only works for iframes, not object/embed/etc.

[domenic]

I mean, embed and object are also kind of deprecated... I guess not formally in the spec.

I tend to think we should either shoot for modern-BC-containers only (= iframe and maybe in the future portal), or we should do all BC-containers (including frame).

[npm1]

@spanicker might have more context here. It appears that we would need to handle other cases in a case-by-case basis. For iframe/embed we'd like to use src, but for object we'd like to use data, and not sure what else can be a browsing context container.

[domenic]

What does Chrome implement?

I think the complete list should be embed, iframe, frame, object.

[npm1]

Ok, I did some testing and it looks like the longtasks are reported as you'd expect, except containerSrc is empty for object (due to the URL coming from data instead of src).

[tdresser]

Given that frame is effectively deprecated, I think we should probably stick to embed, iframe, and object. Does that sound reasonable?