Trying 1.9.0-beta01 'Text context menu' on old version browser (firefox 116.0.2) (JS target) got app crash with exception

TypeError: this._this__u8e3s4__1.get_nativeClipboard_65sjti_k$().read is not a function

It would be nice to have fallback logic for unsupported feature. For example, not shownig context menu.

One more issue related to 1.9.0-beta01 'Text context menu' When right click on text field additional 'paste' context menu item appeared over context menu. It is disabled initially and after several seconds become enabled Using browser Firefox 140.0.4

One more issue related to 1.9.0-beta01 'Text context menu' in mobile browser When press on text field Software keyboard is not appearing When long press on text field context menu appeared with all actions disabled and it is impossible to hide it

Did anyone get the keyboard IME paddings to work on mobile Compose Wasm? Wondering if there's a ticket logged, my search returned nothing.

Is there anything on the roadmap for general performance? I can't quite pin it down but there's probably multiple things going on when I compare a CMP app as an iOS app to one running in a browser. One thing seems to be that it's running at max 60hz. Is there any flag I'm missing or is 120hz still not supported?

for some reason I can't get the gradle tasks to generate the full output needed for a compose web app I run

jsBrowserDistribution

or

jsBrowserDevelopmentExecutableDistribution

and it outputs a

composeApp.js

file, but no index or skiko etc. any ideas how to debug this?

What is the reason of showing squares instead of the default text until custom fonts are loaded? Is it intended or is it going to be fixed? Looks so bad

Apologies in advance if this has already been answered. Is there any way to resize a compose view as the canvas is resize? I.e. user changes browser width, I'm not seeing the compose view resize with it even when dispatching a window.resize event

Whats current state of compose web, possible to use it with common KMP libs? Like Jetbrains, Androidx, Ktor, Koin and such. Or does most libraries omit wasm/web as they did for a while still?

This message was deleted.

When upgrading Compose to 1.9.0-beta01 and Kotlin 2.2.20-Beta2 my compose runtime based project no longer works on JS target (works on Wasm). The runtime error in the browser console in 🧵

Another issue with 2.2.20. When upgrading Kotlin from 2.2.10-RC2 to 2.2.20-Beta2 (or 2.2.20-RC-233) I see IrLinkageError error. More in 🧵

When updated to 1.9.0-beta03 and generated production executable i see skiko.wasm is still present in dist/js/productionExecutable and there is also 7c00bf3a63531ae384d9.wasm that is renamed (to unique name) skiko.wasm. Second one is loaded at runtime. May be skiko.wasm should not exist in dist/js/productionExecutable after build? It is not used. Also in generated production app-name.js file i can see something like Et="file:///absolute/path/in/pc/that/this/js/was/build/skiko.mjs" !!! (How it should be used? It can be sensitive info!)

Normally compose applications should behave the same on all platforms. However I just realized that this is not always the case and may spoil your whole program logic. I developed an application on desktop for better developer experience but actually want to deploy it as a Wasm PWA. This normally works nicely but I now stumbled over an annoying inconsistency. The problem is that on desktop DisposableEffects are always executed when the composition is left even if the user just closes the window completely and thus terminates the application. On the wasmJs platform however this is not the case. If the user just closes the browser window then any pending DisposableEffects are not executed. In my case this had the effect that some important values were not persisted. This inconsistent behaviour may spoil your whole program logic if you rely in this way on the execution of DisposableEffects. I just wrote this up because it may possibly help someone else to avoid this pitfall.

Is Compose Navigation expected to work on WASM? My app loads a landing page, which is a default navigation destination. But as soon as I click a button to navigate further, the WASM target crashes across all three major browsers. This currently happens with Kotlin 2.2.10 and Compose 1.9.0-beta03, but this is not a regression. Its not worked for me with prior Compose releases. The same navigation works OK in the Android and Desktop targets.

I guess it matters to post it here as well 🙂

Hello, all! I have been experimenting with Compose for Web and love the developer experience! I am now considering ways to embedd "Sign in with Google" button. I am currently exploring ways to use

kotlinx-html

to dynamically add code, but have not succeed to display the button this way. Is there a known path to integrate "Sign in with Google" with a Compose for Web application?

does anyone know any alternative to the composeApp.js which is generated? is there any smaller human readable form which can be used to load wasm into a canvas?

Very interesting video !

Hi, I have a small wasmjs webapp, and all is nice, except the initial loading time. I tried showing some splash screen, but for some reason, it has no effect. I've modifed index.html to show some loading animation. And inside my composable i have: LaunchedEffect(Unit) { hideLoadingScreen() } But the loading screen disappear almost immediately, and then i stare at blank screen for ~5 seconds, than my app shows. Any ideas?

How to get geolocation in KMP wasmJs project? window.navigator.geolocation is not found

Hi. I'm trying to run a Compose Multiplatform web project, but I’m getting an error. I’m not sure what’s causing it. Can anyone help me fix this? I've attached more context below in this thread.

How can I create a high-resolution HTML canvas attached to composed so that when I zoom in, the content remains sharp and does not become blurry?

Been getting this error when I try to run the js target of my app. No clue how to debug this yet. Still digging. If you have any idea, let me know

Unable to make field private long java.lang.ref.SoftReference.timestamp accessible: module java.base does not "opens java.lang.ref" to unnamed module @e4e4f1

Anyone else getting

Function 'ComposeViewport' can not be called: No function found for symbol

? in 1.9.0-beta03

I migrated a google map html interop from an older

HTMLView

fom here to

WebElementView

with 1.9.0-rc-01. However, now my markers aren't showing on the correct position when I click on a map. It is "kind of close", but not quite. When panning the map, the marker is pinned to the same geolocation, but when zooming, it moves up and down. (Code in thread - so even when markerPos does not change, it appears to float up and down as I zoom in and out) Any ideas why?

Hi everyone, I've been playing around with Kotlin -Web recently and have a question. What is the difference between the wasmJs and js targets? If I build the UI with HTML (not using Compose ui), will the business logic have the exact same internal behavior for both targets? Or does wasmJs compile the business logic to WebAssembly, while the js target compiles it to JavaScript?

enum class FakeApp(val title: String, val icon: @Composable () -> Unit, val content: @Composable () -> Unit) {
    SYSTEM_INFO("System Info", ::SystemInfoIcon, ::SystemInfoApp),
    ABOUT_ME("About Me", ::AboutIcon, ::AboutApp),
    ;
}

results in

Reference to function 'SystemInfoIcon' can not be evaluated: The call site provides 1 more value argument(s) than the function expects
IrLinkageError: Reference to function 'SystemInfoIcon' can not be evaluated: The call site provides 1 more value argument(s) than the function expects

How do I fix this?

I’m new to the compose-web. Wanted to see if it would be a nice option to start creating applications in although the first component I want to create is already giving issues. The component is a text field with a drop down. Sadly I either have just the JVM working with the up and down arrows for selection with the enter key and WASMJS failing on the enter part and when I add onPreviewKeyEvent plus focusable on the dropdown itself it makes the up and down arrows on both not work correctly anymore (need to press it a few times before it works) Since I am not a great wizard in compose I would love to hear your input. Code in the thread