Kenneth Rohde Christiansen

Basically what the browser supports on at least one of its platforms

Btw looking at those WebHID pending promises, I don't ever see them remove promises as they resolve. Looks like a mistake, or am I missing something?

@Elchi3 I was wondering if you have any input on what supportedSources should expose. Right now it exposes the sources supported by the user agent (browser) but not necessarily supported...

Yeah so we could add a ```Promise getSupportedSources()``` in place of the existing method I think that would be more useful. @rakuco @arskama what do you think? How hard would...

If we decide to do this, we can remove the existing API for now and if we don't make it, we can add this new method after shipping @tomayac you...

Yes, we could support this in the API using someting like entryTypes (https://www.w3.org/TR/performance-timeline/#dom-performanceobserverinit) ie "cpu", "gpu". Thought level 1 is CPU only, we should make sure it can be extended...

I am a bit worried about the word thread as it is not really used in specs (to my knowledge) and APIs, though users talk about main thread. I guess...

@nhelfman I somehow missed this issue you filed. Yes, most certainly, we also intent so work for cases like the one you described and it would be great to get...

There is definitely things to still consider here, as whether our frequency is high enough and future support for GPU pressure. Let's keep it open for now.

I think it is a bit more complicated than that. Some CPUs can quickly recover and some can't - so you might want to analyze the data a bit before...