-
Notifications
You must be signed in to change notification settings - Fork 187
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
Unicode in Brave #196
Comments
Are you using wayland? |
Im using wayland |
It looks like chromium based browsers don't properly handle IMEs when using wayland. Apparently chrome was relying on gtk for its IME processing. Using |
@rvaiya thank you! i'll try it! |
|
Can you clarify by what you mean by 'doesn't work'? Adding I am in the process of trying to figure out what this is, but you can temporarily fix the issue by manually trimming the file to include only the definitions of interest. |
i've installed |
Does brave crash? (it should). If not, then it seems it isn't using gtk4 for parsing. It may be that you are running under X wayland. Can you try the following flags?
|
tried brave --enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4 didn't crashed and issue still persist logs
|
What distro are you using? What version of brave are you running? ( |
version: |
I'm not terribly familiar with NixOS, but my understanding is that packages are hermetically sealed and contain all of their dependencies. Would your brave package have access to gtk4 on the system? I assume you would need to add gtk4 to the brave package itself. |
Closing due to inactivity. Feel free to reopen it. |
Were you ever able to get this to work? Another solution might be to try looking for any |
Good day to you!
Unicode characters works good in terminals, telegram, firefox, thunderbird, etc.

but for some reason it doesn't work in Brave. (but
xkbmap
works fine)Thank you!
The text was updated successfully, but these errors were encountered: