Ok, but what do you mean by "because it's a timer extension"? Do you want the timer to still work on the lock screen? When you use session mode, on locked, your extension can be disabled and re-enabled many times. That's how the shell is rebasing. If keeping the timeout active is your goal here, I don't think that will be precise.

Yes I want the timer to keep ticking. I tested it and it works, the extension does not get disabled when transitioning to lock screen. I know that in a previous version of gnome shell (below 48) the extension would get disabled like you described which defeats the point. Are you saying this is how gs still works? :(

It all depends on the order. Please take a look at the shell code for this: https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/63bf8674ff4a6c480da2ff03ff600094128f1ae7/js/ui/extensionSystem.js#L194-200

Thank you for pointing that out. That's a bummer. :( I guess we'll keep this as is because it will work for some people. Do you know what determines the order of extensions? I just installed arc menu which alphabetically precedes cronomix and everything still works correctly.

It's based on extension order: https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/63bf8674ff4a6c480da2ff03ff600094128f1ae7/js/ui/extensionSystem.js#L268 Anyway, we cannot approve session mode based on the faulty behavior. Also, the key binding is not allowed when you are using session modes: https://gjs.guide/extensions/review-guidelines/review-guidelines.html#session-modes

I disabled the keybindings when in lock screen.

Line 62 `utils/keymap.js` is the keybinding add. Anyway, even removing those won't help to get approval for session modes since this is not a good case for `unlock-dialog`.