marcohu

For the button display, the culprit seems to be https://github.com/deadalnix/pixel-saver/blob/master/pixel-saver%40deadalnix.me/buttons.js#L202 But it seems to be a general problem. Why is always the topmost maximized window used instead of the active...

It's intentional then and not a bug? Than the ticket could be closed. Like the reporter I would indeed expect that the button(s) disappear if e.g. a window is unmaximized....

Should there be a warning at all? Does the timeout affect the execution in any way? If not, why warn about the wrong expectation? My usecase is local execution during...