Description
What problem does this solve or what need does it fill?
It would (I think) allow for the ability to have a game started again after being stopped using AppExit::Success.
This would make it so that you could have a list of games that can be started and stopped at any time instead of bogging down the users device with multiple games running at the same time or forcing the user to reload the page.
What solution would you like?
Allow for App::run() to return on Web.
What alternative(s) have you considered?
Continually doing import("file.js") with variations to the path to trick it into loading the same thing over and over again, which may work, but would constantly be creating new modules which is probably a bad thing!
Also, instead just giving up and forcing users to open a new tab to play the game, but that's no fun!
Edit: Also Iframes. This should work I think, and it is kinda goes against the point right before this since it requires the creation of a page dedicated to the game, but it might be a good tradeoff since it allows for more control on where the game is positioned on the page, makes it easier for other sites to do the same and link to it, and makes it so you could just send the link to the game directly instead of linking to the article/whatever that the game is included on.
Additional context
I had previously made this a discussion because I am bad at knowing what the proper thing to do is.
Other discussion I found that might be related: #11619
I also don't know if allowing App::run() to return would actually allow for the game to be run again, or if the reason that it doesn't return was to prevent people from trying to start a stopped game because of other issues that doing so might cause.