1) There must be multiple browsers open to the application.
2) Start the application and load the page in one of those browsers.
3) Within the first 15 seconds interact with file system lists.
Then once the second browser connects to the application the first browser loses focus and selection of file system artifacts.
What is happening is that the second browser requests file system status when it comes online. The terminal side of the application gets the latest file system status for the given location and then broadcasts this to all browsers, even though it isn't wanted by the first browser containing user interactions. Focus is lost because the existing file system list is destroyed and replaced by the new file system list requested by the second browser.
I have no idea how I would fix this for a minor edge case without introducing considerable complexity.
I thought about this issue through the day and its important to note, but at this time I will not fix it unless I can think of alternate approaches that do not introduce multiple steps of complexity.
In order for this bug to occur:
1) There must be multiple browsers open to the application. 2) Start the application and load the page in one of those browsers. 3) Within the first 15 seconds interact with file system lists.
Then once the second browser connects to the application the first browser loses focus and selection of file system artifacts.
What is happening is that the second browser requests file system status when it comes online. The terminal side of the application gets the latest file system status for the given location and then broadcasts this to all browsers, even though it isn't wanted by the first browser containing user interactions. Focus is lost because the existing file system list is destroyed and replaced by the new file system list requested by the second browser.
I have no idea how I would fix this for a minor edge case without introducing considerable complexity.