Compatibility/Meetings/2023-04-18

Minutes

[Draft] State of WebCompat Report Template Q1 2023 ([doc](https://docs.google.com/document/d/1Bp50F9NrD4uiZ38bELCrBTkHcCxB9Ie-nWJrHvEY3qo/edit#heading=h.qah79c3kt819))
Honza: as I've mentioned last time, we've done several analyses, so I've added a few sections to a draft document with some basic data sources and summaries. We need details filled out and for it to be polished. James can do the interop2023 section, Tom and Simon the Safari/Bocoup section, etc. Hope to have something relatively ready by the end of the week. Next Tuesday we can decide if it's publishable yet. If there are any other sections we'd like to add, or even change or drop some things that are already there, let's go ahead.

Tom: we'll start adding more tests for Android at this point. It landed in https://bugzilla.mozilla.org/show_bug.cgi?id=1805826
Tom: I have a spreadsheet with some of the tests we have and tests we need, that should be a good start.

What's new with JSTracer feature in DevTools, update. (Demo given, of new hotkey control-shift-5 to toggle tracing)

Alex: adding write-to-file support is proving trickier than hoped, but there is a patch semi-ready for logging to stdout with working links. During startup, Firefox will now interpret links passed via the command line of the form `-url "url:1:1"` and open them in the debugger. Also which mode you have enabled now persists across Firefox restarts (stdout vs console). Perf improvements also recently landed for logging to the console, it's like night and day even if stdout logging is still quicker. In addition there is a privileged console API (startTracing) now available to trace chrome JS, but it's not accessible yet from web content (console.jsTrace or similar will take more time to figure out).

Privileged API:

 const {
   startTracing,
   stopTracing,
 } = ChromeUtils.import("resource://devtools/server/tracer/tracer.jsm");

 startTracing({ prefix: "testPrefix" });
 ...
 stopTracing();