Should datalist, option, object, and/or iframe elements be listed in "interactive content"?

[josepharhar]

What is the issue with the HTML Standard?

This came up during the spec review for the customizable select content model: #10586 (comment)

[annevk]

cc @sideshowbarker

[josepharhar]

An example where this might already be an issue is that button elements already allow objects within them, and objects can act as an iframe and are keyboard focusable in chrome.

Content model for buttons:

Phrasing content, but there must be no interactive content descendant and no descendant with the tabindex attribute specified.

@scottaohara

[scottaohara]

one point of clarity:
iframe is already listed as an interactive element. so the question i had is more shouldn't object elements that can be used similarly to iframes be considered interactive too?

if not, then what is it about iframe that makes it interactive, but an object performing the same user experience is not?

But really, with the changes to select / i'm questioning why these wouldn't necessitate an update to option and or datalist to also become classified as interactive elements.