1619660 - Investigate how we can get report of blocked warning messages caused by eager evaluation

Status: NEW

(DevTools :: Console, task, P3)

Description

[Nicolas Chevobbe [:nchevobbe]]

In Bug 1616721, we changed the URL eager evaluation are made in so we can block messages coming from this URL in the console server.
One concern is that some warning messages are only emitted once, and that by not showing the ones from eager evaluation, the user might miss one they would have when doing a true evaluation.

We should check if we could have those blocked messages reported to us one way or another so we can act quickly if we think there's a high chance for the user to miss important messages.

Comment 1

[Nicolas Chevobbe [:nchevobbe]]

Harald, would you have an idea on what we could use to do such thing?

Comment 2

[:Harald Kirschner :digitarald]

Do we have an idea of which messages could be affected by this? These would be triggered by user input and not from rendering sites; so it is a special case already.

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

Logan pointed me to this function calls https://searchfox.org/mozilla-central/search?q=symbol:_ZNK7mozilla3dom8Document13WarnOnceAboutENS1_20DeprecatedOperationsEb&redirect=false , so it could be a lot of different things

Comment 4

[:Harald Kirschner :digitarald]

So a big chunk of deprecated APIs that still work but shouldn't be used in content. Given that, I can't imagine a case where a console expression should trigger a warning once and where not having the warning is bad for the developer. Let's see if we get any reports or more specific problem cases.