2 ms·
From quickly checking the code before the reports, you seemed to be first checking for the height thing, and prematurely returning, before running any profiling
by goldfeld 14y ago
From quickly checking the code before the reports, you seemed to be first checking for the height thing, and prematurely returning, before running any profiling. Wouldn't you avoid these problems if you first checked for the surer stuff, and then checked the height?
- afschwartz 14y ago@goldfeld absolutely. However, the profiler check mucks up the console output so I was hoping to use it as a fallback. For now I've made it experimental and will keep it that way until we can resolve the issues you pointed out. (https://github.com/adamschwartz/chrome-inspector-detector/is... https://github.com/adamschwartz/chrome-inspector-detector/is...)