Its not designed with a low-spec system in mind let-alone be browser based. This is a problem where trying to get into the menus, or activating the puzzle camera/cursor is not properly. The first instance of something wrong is when switching to the reticule it doesn't hide the default cursor. I assume this all must be associated with in the underlying Tools i am using. Despite all the code digging I do I can't seem to narrow down the difference between the build and the editor behavior. The interwebs tells me it might have to do with how each handles the code-execution order, but I'm not about to assess what order to setup this beastly notion. Other theories I've had are some particular seemingly useless element being accidently removed as I cleaned up my project, to that I spent some time reworking the menu-system. No luck with that. I have a nice little 'walking sim' which does have an end condition, so at least I'm not without an entry completely... which was going to be case when the Loading screen wouldn't go away.... (same issue, but I was able to remove the loading screen and now it just has a short pause/freeze between menu and game).