Hi everyone! We're busy evaluating WasmJS (with Compose) for use for the development of our admin p...

# webassembly

[Steyn Geldenhuys]

Hi everyone!

We're busy evaluating WasmJS (with Compose) for use for the development of our admin portal webapps. But first I'm evaluating it in non-critical side project.

I've noticed a few things:
1. Text is not selectable in a browser
2. In OutlineTextField possible all TextField components, do not show the carret once typing has started
3. Pasting into a TextField does not work - simply a 'V' is inserted if I use a crtl+v
4. No right click context menus
5. On mobile when touching a TextField the soft keyboard is not triggered
I'm still pretty new in my Wasm journey in general, but I guess given that Skiko is rendering this on a canvas and not all interactions are implemented yet. I guess it's still a bit early to expect this all to work? Or am I missing something?

And FYI, I'm using the following versions:

[versions]
kotlin = "1.9.21"
compose = "1.5.11"
compose-compiler = "1.5.6"
compose-plugin = "1.6.0-alpha01"

[Steyn Geldenhuys]

Also, sorry for sending and deleting this message a few times, I haven't really used Slack before. 🙂

[Bharat Kumar]

Hi @Steyn Geldenhuys how is focus and hover effects working there did you check that ?

[Steyn Geldenhuys]

Hi @Bharat Kumar no I haven't checked it yet, I'll have a quick look

[Michael Paus]

1. Text is not selectable in a browser
This is the default behaviour of all platforms. See:
https://developer.android.com/jetpack/compose/text/user-interactions

[Oleksandr Karpovich [JB]]

2. Is already fixed in skiko, waiting for build.
3. Work in Progress
4-5. Planned to fix

[Steyn Geldenhuys]

Thanks @Michael Paus when wrapping a Text composable in a SelectionContainer it is still not selectable when running in the browser, but when I run it as a desktop app it is selectable. I guess there's a bug there.

[Steyn Geldenhuys]

@Oleg Yukhnevich thanks for the info! I'm looking forward to it. 🙂

[Steyn Geldenhuys]

@Bharat Kumar the onPointerEvent modifier seems to be working correctly. FYI here's a short video showing this.

Screen Recording 2024-01-05 at 14.43.58.mov

[Michael Paus]

@Oleksandr Karpovich [JB] Are there plans for 1. too? 🙏

[Oleksandr Karpovich [JB]]

Sure, the Text wrapped in SelectionContainer should behave similar to dekstop and other targets. So it's a new bug we didn't know before 🙂

[Steyn Geldenhuys]

@Oleksandr Karpovich [JB] I'm happy to file a bug, just point me in the right direction.

[Oleksandr Karpovich [JB]]

Thanks! We have issues tracker here - https://github.com/JetBrains/compose-multiplatform/issues

[Steyn Geldenhuys]

Great thanks! I'll file it there.

[Michael Paus]

I just realised that on desktop a Text (actually a ClickableText in my case) wrapped in a SelectionContainer is selectable but not copyable via keyboard (via right-click context menu “copy” works). Is that normal? I am quite sure that worked before. (Compose 1.6.0-dev1357)

[Oleksandr Karpovich [JB]]

@Michael Paus I don't remember trying such a use case myself. quickly looking into the code, I don't see SelectionContainer handling Ctrl+C, Cmd+C.
If you can find a version when it worked, then it's a regression.

[Michael Paus]

Maybe I am wrong on the keyboard part and have always used the context menu in the past. But I am sure users would expect to be able to use the keyboard for that too.

[Steyn Geldenhuys]

@Oleksandr Karpovich [JB] issue opened: https://github.com/JetBrains/compose-multiplatform/issues/4103

[Michael Paus]

And here is the follow-on issue https://github.com/JetBrains/compose-multiplatform/issues/4104