Oleksandr Karpovich

Since the issue only happens on Windows AND with binaryen enabled, it's likely that the core cause is not in Compose. Since the issue is already reported in Kotlin tracker,...

Thanks! It's a known issue. It will be fixed in k/js: https://youtrack.jetbrains.com/issue/KT-60635/K-JS-Class-internal-methods-may-clash-with-child-methods-from-other-module-that-have-the-same-name As a workaround you can add `kotlin.incremental.js.ir=false` to your gradle.properties

We'll add a workaround on Compose side: https://github.com/JetBrains/compose-multiplatform-core/pull/734 So it should start working without `kotlin.incremental.js.ir=false` in the next compose builds.

Yes, we plan to address it after we address the issues which have no workarounds.

@Omico you might try to use Local Font Access API https://developer.mozilla.org/en-US/docs/Web/API/Local_Font_Access_API, it's experimental and available only in Chrome and Edge.

Compose Multiplatform 1.7.0-dev1721 is out and it contains the Fonts fallback provider change: https://github.com/JetBrains/compose-multiplatform-core/pull/1400 (please take a look to see a usage example). That version of Compose for Web can...

> several independent extensions for an Element Could you please show some code example, even hypothetical? How those extensions are added/applied to an element. I'm wondering if your extensions could...

I'd like to discuss an alternative, which doesn't require the implementation changes: ```kotlin Div(attrs = { //.. }) { DisposableEffect(1) { val listener = {...} scopeElement.addEventListener("click", listener) onDispose { //...

> Besides, it is not direct usage of DisposableEffect, because it has been created to track some value (as I understand) which means that it will be more complex in...

```kotlin DisposableEffect(0) { if (some) doSome() else doOther() onDispose {} } ``` This won't work - right. But if you have extensions, you can have: ```kotlin @Composable fun Foo() {...