-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SettingsExpander not showing title and description on Wasm/Uno #393
Comments
#321 might be related. @MartinZikmund does this ring a bell? |
@niels9001 not really, it sounds like a data binding issue, we will have to investigate |
Any update on this @MartinZikmund? This is one of the best new controls in WCT, it would be great if we can use it in Uno as well. |
We will make sure this is handled asap, most likely though the fix will have to be on the Uno Platform side, and we also need the WCT 8.1 update which will include Uno 5.x support 👍 |
@MartinZikmund |
Could this have been fixed with #452 ? Would someone be able to verify? |
This is how it's rendering for me on https://toolkitlabs.dev/ |
That's SettingsCard, not Expander. Could you try that to see if the issue is resolved? Maybe one of the recent Uno updates fixed the issue.. |
Ah sorry. Yes it's still broken it seems. |
Hi 👋 I am looking into this issue from the Uno Platform side. Who can guide me in compiling and running the cc: @niels9001 |
@ajpinedam You can find our Quick Start guide here, otherwise we're available on GitHub and Discord if you run into issues! |
@ajpinedam any luck in investigating what might be going on here? Were you able to setup and run the projects from our repo? |
@michael-hawker This may have gotten fixed with latest Uno dev bits. Any chance you could double check? |
@michael-hawker, as @Youssef1313 mentioned, this was fixed. Please use one of the latest dev versions of Uno whenever you can and validate the fix. |
The SettingsExpander is not showing title or description when running on Wasm.
Originally posted by @lukasf in #383 (comment)
The text was updated successfully, but these errors were encountered: