-
Notifications
You must be signed in to change notification settings - Fork 16
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
Extension not working as of GNOME 42.0. #49
Comments
This probably doesn't work because the https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/00ccea48a |
Thanks so much for this followup, @lzhang. I don't know much about GNOME customization, but maybe there's some other internal method we could override? Anyway, I'll try some experiments when I get a chance. If you have more knowledge and have some ideas, I'm all ears! |
@kfogel : The only function of the |
Thank you for these tips, @G-dH! |
@kfogel : To be specific, the best solution is to override the popup class with an empty class with only the display() function. |
Got it, @G-dH. (It may be a while before I have a chance to do this, due to some other obligations right now, but I very much appreciate these tips -- they'll save a lot of time when I finally get a moment to enter the code/test cycle.) |
Looking forward to this. FWIW, this one works for me in GNOME 42: https://extensions.gnome.org/extension/4980/disable-workspace-switcher/. |
Good to know about that one, thanks @evenfrost! It will be at least weeks, perhaps months, before I have any chance to look at this issue (due to some family stuff). If you're considering working on it, please go for it! I don't want to be a blocker. |
Hi, @windsorschmidt. I upgraded recently and Debian
testing
distro brought in GNOME 42.0......so naturally I updated this extension locally in the usual way:
However, the extension is having no effect. I can see in
gnome-extensions-app
that the extension is turned on, as expected. But I still get a workspace switcher popup.I asked about this over in GNOME Discourse, because the visual appearance and location of the popup have changed a bit, and Florian Müllner confirmed that even though the appearance and location have changed, the same code should still work to suppress the popup.
Do you have any idea what's causing the extension to suddenly not work? For all I know this might even be a GNOME bug, or maybe there's some new compatibility shim we need to place in the extension code (like the "// Backwards compatability with 3.0.2" shim you already have in
extension.js
), but I'm not even sure how to start debugging this.The text was updated successfully, but these errors were encountered: