Anyone have issues using the `Iframe` builder in 1...

# compose-web

[Chris Sinco [G]]

Anyone have issues using the Iframe builder in 1.0.0? It seems that IntelliJ can't resolve the attributes within the attribute builder which is odd since you can see the inlay hints are registering and I see them in the definition source in the IDE...

[Chris Sinco [G]]

Welp I "reimplemented" it again since I couldn't get it to build, even though the code looks very redundant 🤷🏻‍♂️ https://github.com/c5inco/portfolio-compose/blob/main/src/jsMain/kotlin/com/c5inco/portfolio/components/Iframe.kt

[[JB] Shagen]

Нey Chris! It looks like there’s a room for improvement on our side.

The thing is that we are passing to the element build AttrBuilderContext<HTMLIFrameElement> which is not the same thing as HTMLIFrameElement

for some context, like, say, HTMLImageElement we’ve explicitely added extensions like

fun AttrsBuilder<HTMLImageElement>.alt(value: String): AttrsBuilder<HTMLImageElement> =
    attr("alt", value)

but for some we don’t.

I think that’s a fair assumption that user still expect this behaviour so we’ll consider how to address this.

The cheapest thing would be to just add extension functions for everything but we’ll see whether we can do something better.

[Chris Sinco [G]]

Ah I see - yeah that is much simpler than create another element. I removed my Iframe function and just added three extensions instead!

[Chris Sinco [G]]

Should we just add these extensions to source? https://github.com/c5inco/portfolio-compose/blob/main/src/jsMain/kotlin/com/c5inco/portfolio/components/Extensions.kt