no, it didn't. It doesn't happen when Litestep isn't running as shell either. If I run Litestep on top of explorer, the problem goes away immediately.