Fwd: Netmonitor.html Workweek Summary

[Fred Lin]

Hi,

We just finished the Netmonitor workweek (Fred, Honza, Ricky) in Taiwan
last week, plenty of discussions have occurred, and we have good progress
for what's should be going on for Netmonitor.

Here they are:

- We have Prove-Of-Concept branches[1][2] to prove we can run netmonitor
on browser tab 🎉
- We decide to stick on mozilla-central and use similar approach as
inspector to run the netmonitor in a browser tab
- We stopped Netmonitor.html phase I work immediately (convert XUL to
HTML, MVP 100% completed)
- We'll start Netmonitor.html phase II (To run Netmonitor on a browser
tab, so we can debug Netmonitor with any browser's devtool) from this week
- All phase II bugs are filed in meta-bug,
<https://bugzilla.mozilla.org/show_bug.cgi?id=1348737>some
low-hanging good-first-bugs are ready to grab
- Have a meeting with jlaster, we'll land Netmonitor.html related
share modules into `devtool-module`
-

We’ve triaged all new Netmonitor bugs 🐞
- We agree that we should re-triage webconsole:http-inspector related
bugs to Netmonitor
- We also discussed about service-worker related UI and features with
platform engineers, no recent plan from devtools team yet


cheers
--
Fred


- [1]
https://github.com/gasolin/devtools-core/tree/netmonitor.html/packages/netmonitor
- [2] https://github.com/rickychien/netmonitor.html/

[rch...@mozilla.com]

We're planning to adopt the approach like inspector and m-c workflow will work as usual. During this period of time, there are nothing changed to netmonitor contributors who have been familiar with mozilla-central workflow and keep contributing to devtools.

Today, we just kicked off Netmonitor Phase II project with Marco. Our Phase II breakdown tasks has prioritized and Tracking Dashboard will be discussed in tomorrow. See also Netmonitor.html work week notes for details.

Thanks!

[Alexandre poirot]

Hi Fred,

> - We have Prove-Of-Concept branches[1][2] to prove we can run netmonitor
> on browser tab 🎉

Note that, like the inspector, with some tweaks to netmonitor document
and init script, you can make it run in a tab, with chrome privileges.
(It reduces the amount of refactoring needed)
See this bug, where I made the inspector run in a tab, from its chrome URL
https://bugzilla.mozilla.org/show_bug.cgi?id=1297758
The drawback is that you have to go through about:debugging to craft
the chrome URL with the right parameter to designate which tab you
want to debug.
But at the end it is somewhat similar to the launchpad step.
Also note that F5 works if you happen to install the devtools addon:
https://developer.mozilla.org/en-US/docs/Tools/Contributing/Contribute_on_nightly

> - We'll start Netmonitor.html phase II (To run Netmonitor on a browser
> tab, so we can debug Netmonitor with any browser's devtool) from this week
> - All phase II bugs are filed in meta-bug,
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1348737>some
> low-hanging good-first-bugs are ready to grab

The title of this bug, and the description you have giving here don't
match the bug list it contains at all. It seems to be about papercuts
and important bugs to fix. Whereas you seem to describe it as what is
needed to run netmon in a unprivileged tab via launchpad?
Is Q2 focused on fixing bugs or continue the refactoring in order to
run it via launchpad?

[Fred Lin]

Alexandre, in our prototype we can use devtools-launchpad directly to run
Netmonitor in a browser tab without chrome privileges, and its not too far
from doing so in mozilla-central

The title of this bug, and the description you have giving here don't
> match the bug list it contains at all. It seems to be about papercuts
> and important bugs to fix. Whereas you seem to describe it as what is
> needed to run netmon in a unprivileged tab via launchpad?
> Is Q2 focused on fixing bugs or continue the refactoring in order to
> run it via launchpad?
>

The top priority for me and Ricky would be run netmonitor via launchpad,
marco use this meta bug to track project status so we put the rest
important bugs to fix into this meta bug as well.