Could you please run ./gradlew :mpp:jbApiDump and add the update to this PR too?

done

I see a lot of unrelated changes in the new api dump (for example for material3). I'll investigate.

I'm not sure why it generate such api dump in your case. (Do you have unstaged changes? I doubt, but that would exaplain it)

When I tried to update the dump in your branch it resulted only in one change:

// Targets: [js, wasmJs]
final fun <#A: org.w3c.dom/HTMLElement> androidx.compose.ui.viewinterop/WebElementView(kotlin/Function0<#A>, androidx.compose.ui/Modifier?, kotlin/Function1<#A, kotlin/Unit>?, kotlin/Function1<#A, kotlin/Unit>?, kotlin/Function1<#A, kotlin/Unit>?, androidx.compose.runtime/Composer?, kotlin/Int, kotlin/Int) // androidx.compose.ui.viewinterop/WebElementView|WebElementView(kotlin.Function0<0:0>;androidx.compose.ui.Modifier?;kotlin.Function1<0:0,kotlin.Unit>?;kotlin.Function1<0:0,kotlin.Unit>?;kotlin.Function1<0:0,kotlin.Unit>?;androidx.compose.runtime.Composer?;kotlin.Int;kotlin.Int){0§<org.w3c.dom.HTMLElement>}[0]

I think we can eliminate that change by keeping WebElementView experimental as it was. Experimental API doesn't apear in api dump.

If you return @ExperimentalComposeUiApi on WebElementView back, then you can drop the api dump commit.

I'm not sure why it generate such api dump in your case. (Do you have unstaged changes? I doubt, but that would exaplain it)

none that affect Material 3 sources or foundation Locale. I just did what you suggested since I cannot seem to make it work without it or not updating api dump. If you could do it from your side for it to work would be better but for now this is what I can do