> What does "display/compositor fragmentation" mean to end-user?
My 1Password FireFox extension (ubuntu 18.04 LTS) doesn't work on X unless I log in through the website but it works just fine on Wayland.
My 1Password FireFox extension (ubuntu 18.04 LTS) doesn't work on X unless I log in through the website but it works just fine on Wayland.
Hey there! Beyer from 1Password here. It sounds like your issue might be related to my post here: https://goo.gl/cdhFbz
The good news is the underlying bug that was "breaking password fields in Firefox" was recently resolved. You can read about it here: https://goo.gl/uFv5rL
If you are still having an issue using 1Password X after updating gnome-shell, please reach out to us at support+x@1password.com, and we'd be happy to help!
Thanks for using 1Password!
The practical implications of what it means to the end user is that companies/entities that write any GUI-enabled software for Linux are forced to make decisions about what(if any) OS they'll support.
And just like that, we've waded into "cracking open the window manager" just to figure out what's going on.
Edit: akiselev said 1Password, not LastPass. My mistake. Interesting that I experienced this same issue with LastPass.
After I login through the 1password website, the extension window opens just fine so it might be some input security service, but how would a Firefox extension even have access to a system service like that except through Firefox's built in APIs?
With keepassxc you have native application and extension, that communicate together via socket. The native application can use whatever native APIs it wants.
However, back to you. What's more weird, if it is pure Firefox Webextension, that Firefox (still by default) launches as X11 application under Wayland, so the extension should have no way to know the difference.