Byond sometimes reloads the dom when processing a window.location="byond://" or window.lo style link

ID:2256651
 
Jun 10 2017, 7:59 pm
BYOND Version:511
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 60.0.3112.24
Applies to:Dream Seeker
Status: Open
Issue hasn't been assigned a status value.
Descriptive Problem Summary:
Somethings when processing a window.location="?blah" etc javascript command byond reloads the same page fresh, causing such commands to retrigger if they were set to run on page load.

It seems to be related to how it times with the loading of resources or sending of browser assets using browse_rsc
Jun 12 2017, 12:42 pm
Is there any other info that might narrow this down for me? I know a test case might be difficult to arrange, but something that's intermittent is going to be fairly difficult to catch, I suspect.
Jun 12 2017, 3:50 pm
Its on client connection.

I do know that doing browse() to a window that then sends a topic on load using window.location immediately after a client connects causes all sorts of issues, verb changes don't process, etc, so its likely related.

anywho, I removed our new browse() based output control system away from verified asset loading and it fixed the issue.

this is what was used:

    client << browse({"
    <script>
        window.location.href="?asset_cache_confirm_arrival=[job]"
    </script>
    "}, "window=asset_cache_browser")


It's used to allow us to passively load assets if we don't want them to block other browse() calls, this prevents resource/asset heavy html windows from slowing down browse() calls that don't rely on them. It was created by /vg/ initially. (its also used when doing assets for output() operations).

Some doot put the managed output control system on it, and it started causing all sorts of issues since that loads at client connection.