search

whatwg / console

Console Standard
https://console.spec.whatwg.org/
Other
274 stars 70 forks source link

console.context() #193

Open foolip opened 3 years ago

foolip commented 3 years ago

In the spirit of https://github.com/whatwg/console/issues/27 and https://github.com/whatwg/console/issues/74 I'm filing issues about two additional console members I've spotted as part of https://github.com/foolip/mdn-bcd-collector/issues/917.

console.context(name) is available in Chrome and Node.js, and returns a new object with a lot of the console members. This test gives some clues about what it does: https://chromium.googlesource.com/v8/v8/+/23d0a6a5125d407655f2b7f6bb7263b4e05019d8/test/inspector/runtime/console-context.js

It looks like console.context('bla').log('hello') doesn't log anything in Node.js, but logs "hello" just like console.log("hello") would in Chrome.

Does anyone recognize what this is, and would it be useful to standardize? I expect not, but want to check.

nchevobbe commented 3 years ago

it was added as an experiment a while ago in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=728767 it does provide a nice way to filter logs (as shown in https://twitter.com/hashseed/status/1337709432994750464)

we don't have such thing in Firefox as it's not part of the standard, but I can see it being useful

domfarolino commented 2 years ago

Interesting, it is a shame that it was never standardized in Chrome. I've posted https://groups.google.com/a/chromium.org/g/devtools-dev/c/umeCeS3Bgcs to see if I can get someone from the Chromium DevTools team to lend a hand here, especially since @nchevobbe seems to think that this would be useful, and thus we have a shot at getting multi-vendor support.