I have an application with a very complex table view that doesn't trigger a double click event when using Chrome on Windows 10 with a high DPI display. It works without issue when using a non-High DPI display or when using a Mac with a retina display. It also works without issue when using Firefox on both Windows and Mac with a high DPI display. I have other table views that are less complex in the same application and double click works without issue. I'm not really sure how to fix this issue. It appears that when you simply click the table view there is a slight delay until the selection appears when using Chrome/Win/High-DPI but not during any of the other combinations. Thus, I suspect the double click isn't working due to a performance issue in Chrome. I suppose I could just wait and see if Chrome improves but I really would like to fix the issue since I have no idea if it will ever get better on the Chrome/Win/High-DPI combination.
Since I think it might be performance related I have attached a zip file with a performance profile recorded from Chrome/Mac/Retina and one from Chrome/Win/High-DPI. This illustrates the profile for both a successful double click (ChromeMac.json) and one where the double click did not occur (ChromeWindows.json). On the ChromeMac.json profile the double click attempt starts at 2604ms while on the ChromeWindows.json profile the double click attempt starts at 3150ms. I've looked at these profiles fairly closely but I'm not really sure what I should be looking for. If someone could take a look and let me know if you think there is something I can do to fix this double click issue I would greatly appreciate it.