Open Bug 1499699 Opened 3 years ago Updated 3 years ago
.profile() should return a promise, resolved when the profiler actually started
With the current API it's difficult for the user to know when the profiler actually started. There's 2 solutions to this: 1. return only when the profiler started. 2. return a promise that would be resolved when the profiler started. I think Chrome is doing 1. (although I couldn't really get this to work in current Chrome versions). But because this isn't standardized and isn't supposed to be cross-browsers, and at this time and age, I think we should return a promise.
From :baku, we should file a spec bug in https://console.spec.whatwg.org/ before implementing this, if only to specify that this isn't supposed to be cross-browser, or that it should/shouldn't be exposed to web content.
Related on if this worth the investment: https://github.com/whatwg/console/issues/27#issuecomment-289312546 , also mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1499694#c4
You need to log in before you can comment on or make changes to this bug.