A <video> element is created and attached to the page entirely
via JS, after a delay, with its src assembled from string pieces at
runtime - so static-html-regex finds nothing (no literal URL in the
source) and there's no element for browser-network-sniff-style
traffic sniffing to misattribute, since the one true signal here is
the rendered DOM itself. browser-dom-scan should find
this one by reading the <video> element's resolved
currentSrc. (browser-network-sniff will
likely also succeed here, since loading a real video always
generates a real network request too - that's expected, not a bug.)