Initiating an action from the client(ive tested Click() and verbs which worked, sleeping and calling browse() again did not cause this issue) that calls browse() with a script to call alert() via JS while a JS alert() is already open causes dreamseeker to lock up
Numbered Steps to Reproduce Problem:
1. Commit an action such as a verb which calls browse() which calls alert() via JS
2. Leave the alert open
3. Commit an action such as a verb which calls browse() which calls alert() via JS
4. (if connected to dream daemon instead of running as file) Gets an empty error box with the title of "dreamseeker".
5. Dreamseeker becomes a zombies and locks up, UI still works but buttons and movement keys don't do anything.
Code Snippet (if applicable) to Reproduce Problem:
Full code (single file):
/mob/verb/clickme()
set name = "Click me twice but dont close the alert pop up"
usr << browse("<script>alert(1)</script>", "window=wtf")
Expected Results:
Two alert boxes or an alert box after the first one is closed
Actual Results:
Dreamseeker displays a cryptic error and hangs
Does the problem occur:
Every time? Or how often? Every time
In other games? Replicatable in a simple test case
In other user accounts? Yes
On other computers? Yes, tested with the help of Asd
When does the problem NOT occur?
When using sleep(1) to call browse() again in the same "action" (verb/Click()/we)
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Occured in 513.1542 and 514.1557, unknown before that
Workarounds:
I'm not sure why anyone would want to call alert like that, so try not doing that
