-
Notifications
You must be signed in to change notification settings - Fork 743
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
[WASM] TextBox does not properly keep the focus when in a Flyout/Popup #18790
Comments
Thanks Dierk. We appreciate the time you're spending entering issues. As you know, we're prioritizing issue based on our enterprise clients and we'll take a look at this issue when possible. |
@jeromelaban to be clear: this is not just an issue but a regression. As such, this was working before and now no longer is working. I took the liberty to reflect this on the title of my report. Please let me know if you felt this is not a regression. Thanks |
Thanks. This is not an AutoSuggestBox issue, but rather a focus issue for This is a specialized repro: https://playgroundcanary.z19.web.core.windows.net/#92ea19af which uses Uno 5.6-dev. |
Thanks @jeromelaban. That makes sense, since we saw 'weird' issues related to Nevertheless this is a regression, correct? |
Thanks for taking care @ramezgerges. We'll run tests as a build is available... |
@ramezgerges I just upgraded to 5.5.87 but found that the issue persists. What am I missing? |
This PR is not in any stable release (yet). You can try with a recent dev version (e.g. 5.6.0-dev.1063). |
@DierkDroth this fix will only be present in 5.6 when it will be released. |
@jeromelaban @ramezgerges thanks for clarification. |
Current behavior
Please see repo below: when upgrading from UNO 5.2 -> 5.3 the AutoSuggestBox is screwed up when clicking before starting to type: the selection logic no longer works. Same when updating the repo to .NET 9 and latest UNO 5.5.
Minimal.zip
@jeromelaban my team and I again spent a lot of time chasing down this regression. Together with the other regressions I reported earlier (here and here) we're still forced to stay with UNO 5.1 (!). I'm happy to continue investing resources and time in chasing down UNO regressions, but I also would appreciate if the regressions would be taken care of in not too far future. Thanks in advance
Expected behavior
No response
How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
None
Environment
Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia
NuGet package version(s)
No response
Affected platforms
No response
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: