As discussed on https://github.com/w3c/webdriver-bidi/issues/393 the log.entryAdded event should only be emitted for console API calls that actually use the printer. Otherwise they are omitted.

A test is added via the next wptsync bug 1866709.

I'll have a look and check which APIs are affected. We can have a black list of methods when we do not want to send a log.entryAdded event. We should check the following:

• When time() is called twice it prints an error
• groupEnd() doesn't print but with devtools ui we might want to have this

Given that this is a P3 bug lets investigate when we actually start working on it.

(In reply to Henrik Skupin [:whimboo][⌚️UTC+1] from comment #1)

I'll have a look and check which APIs are affected. We can have a black list of methods when we do not want to send a log.entryAdded event. We should check the following:

• When time() is called twice it prints an error

Currently, time called twice doesn't send an event for an error because it looks like it's generated on the DevTools side. I'll take a look at it in the scope of bug 2005054.

• groupEnd() doesn't print but with devtools ui we might want to have this

Per spec, groupEnd shouldn't send the event, but I agree it might be useful, so I've created the spec issue for it: https://github.com/w3c/webdriver-bidi/issues/1097.

Verify that "console.clear" doesn't trigger "log.entryAdded" event.

https://hg.mozilla.org/mozilla-central/rev/e45e4d9f6900
https://hg.mozilla.org/mozilla-central/rev/311ebec6930f