David Vassallo

Hey @psiinon I've been trying to reproduce this but I'm running into another issue which I think may be browser related and wanted to see if you came across it....

To be honest so do I, this was the first time I did the "manual launch" since my second machine didn't have ZAP. Ok so i'll try reproduce this cache...

The site I was accessing is [https://example.com](https://example.com), and my HUD options are exactly as shown by @dscrobonia because I had to enable "Allow unsafe evals" while doing VueJS development.

Just tried same setup (manually launched and proxy set up) with Chrome and it works - no changes to ZAP... suspecting an FF issue... PS this refers to the CSP...

Ok this is a bit of a tricky one, that I think is actually related to #199 . Let me step through this a bit: **Aspects of the problem** I've...

In fact I was looking for #119 because I was sure you guys must have come across the subsequent issues. I think that this issue is in fact another part...

I see, FF is being sneaky here. Makes sense - the rand number is a good smoke test to figure it out! :)

Actually there is a way around this - and it's been staring me in the face the entire time. As you say @dscrobonia you'll get two random numbers being logged...

What if we move from 3 separate iframes (one for drawer, left + right panel), to a single iframe that contains the entire HUD floating above the target page? That...

Didn't think of that - d'oh! But doesn't matter, since we can inject whatever we want into the page we can use the same concept but just use an injected...