Comment 1 for bug 1569960

When we talked earlier, I think you said that after you refreshed the UI the option to change the range went away.

I think the root cause of this issue is most likely that the subnet cached in the UI did not get updated after the initial range was defined. (most likely an issue with the trigger the websocket is listening for)

It's also possible that the behavior will change with the latest code, since showing those fields is based on whether or not a suggestion for a possible dynamic range is seen in the incoming JSON from the server. So it would be good to try to reproduce with the latest code, now that the fix for bug #1569984 has landed.

Meanwhile, I'll manually test and try to reproduce this bug.