Jonathan Kingston

After initial testing of google.co.uk I see .com being a first and third party in my storage. We should address how these are stored and drawn.

@biancadanforth if the first party has a service worker then it might decide to load scripts/images/css in the page which it could control in the serviceworker. This from my testing...

@biancadanforth the nested iframe case is an issue, we need to make sure that we attribute third party requests to their top level frame first. (We could think about capturing...

@biancadanforth it would be good to create a page which links to each test if you could that would help anyone else needing to debug this rather than comment bits...

Please don't close this for now (especially as the task here was to allow us to distinguish the third parties loading third parties when blocking, that is the actual work...

So it looks like the worst comes from when dragging a node: https://github.com/mozilla/lightbeam-we/blob/master/src/js/viz.js#L375 I see in some cases requestAnimationFrame even on a powerful machine take +150ms I think there are...

I managed to get the graph vastly faster by removing the manual ticking without causing obvious bugs. My hunch is we should be doing something smarter there with ticking and...

I think we might have just made this worse with the latest update. We should look into querying the history in chunks before rendering to reduce the time to showing...

Hi @maqboolkhan so the code of the previous add-on is available: https://github.com/mozilla/lightbeam We essentially want to reimplement that code here and the interactive nature of opening and hiding the panel....

Super excited you both found this :)