We can get a higher precision timestamp from microSecondTimeStamp, which will be consumed
in the console client to re-order messages.
This fixes an issue where different type of resources (console-messages and error-messages)
emitted during the same timestamp would not appear in the order they should be in.
A test is added to make sure the fix is effective.
Differential Revision: https://phabricator.services.mozilla.com/D155546
This is quite similar to the error messages watcher, except that we call
ensureCSSErrorReportingEnabled after retrieving the cached messages.
Resource no longer includes `errorMessageName` and `isPromiseRejection` as it
makes little sense for the CSS warning.
The existing resource test is updated to run with and without the server support.
Differential Revision: https://phabricator.services.mozilla.com/D83047
Removes "exception" and "script" as those properties are unused outside tests and going away.
Corrected the definition of "error", which was wrong because errorFlag == 0.
Differential Revision: https://phabricator.services.mozilla.com/D66508
I had problems running this test locally and it turns out cssErrorReportingEnabled is not
set/unset correctly. Thanks to Boris for pointing that out.
Differential Revision: https://phabricator.services.mozilla.com/D64415
nchevobbe