Why "should" disable? Doesn't it work?

It works fine with the current Artful Aardvark daily build, i will change the description when Ubuntu 17.10 will be frozen enough

Isn't it enough to disable the extension via the software center or the extension-settings?

The mecanism of the Ubuntu 17.10's default session is like the "GNOME Classic" session in Debian/Fedora: there are extensions but GNOME Tweak Tool (or gnome-shell-extension-prefs, or even dconf-editor) can't handle their (des)activation.

Sorry for the long delay but we're being extra careful with all the ubuntu-stuff. In what manner is gnome-tweak-tool not handling it? Can we do something on that side?

i don't know how to describe in english in what manner it's not handled, so i prefer to illustrate it in video https://www.youtube.com/watch?v=Hb3OsMi8dOE Didier Roche (from the Ubuntu desktop team) told me my extension was fine, but that i should report a bug concerning the behavior of GNOME Tweaks (if the switch is inoperative, it shouldn't be operable). I'm not really qualified to know if you can do something about this: "impossible to desactivate" extensions are not a specific ubuntu-stuff, the same issue happens if a "GNOME Classic" user want to disable an extension like, for example, "apps-menu@gnome-shell-extensions.gcampax.github.com".

Ok. I'll approve it. Please file the bug against gnome-tweaks as suggested. Always better to find a solution that works for everybody :)