In that case my guess is wrong, or at least off, because that sounds like an orphaned component, or perhaps a logic misfire corrupting the state with the effect of partially activating a notification tray or something of the sort.

In the worst case, it could be a viewport dim calculation bug that has nothing to do with Voyager. IME those can persist for a long time, forcing developers to work around it.

If the behavior can be reproduced in a browser, you could use the built in devtools to narrow it down quickly.