Re: [w3ctag/design-reviews] State extension for JS Self-Profiling API. (Issue #682)

Just taking another look at this at our face-to-face. 

I'm still concerned about the multi-stakeholder issue - ChromeStatus shows no additional implementer interest.

From @atanassov : What is the story around user consent – because essentially you are using cycles on the user's device. Should it be gated behind a permission? 

From @cynthia : what about main thread CPU starvation caused by a worker or an external process? Also `ProfilerTrace` and others should be annotated as serializable. Also why a document policy over a permission policy?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/682#issuecomment-1077572984

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/682/1077572984@github.com>