Same as for application running under xwayland, unicodes are not working on Chromium when running it with the ozone wayland platform. Though for some reason it's working under the x11 platform.
chromium --user-data-dir=/tmp --enable-features=UseOzonePlatform --ozone-platform=wayland # not working
chromium --user-data-dir=/tmp --enable-features=UseOzonePlatform --ozone-platform=x11 # working
Indeed, chromium seems to have opinions on what keysyms are valid. I have pushed a81540b7d4920566ad271236ca88befc0002b462, which seems to at least fix this on ungoogled-chromium_91.0.4472.164-1.1
Same as for application running under xwayland, unicodes are not working on Chromium when running it with the ozone wayland platform. Though for some reason it's working under the x11 platform.
chromium --user-data-dir=/tmp --enable-features=UseOzonePlatform --ozone-platform=wayland
# not workingchromium --user-data-dir=/tmp --enable-features=UseOzonePlatform --ozone-platform=x11
# working