Working on a preact app, presumed it was preact doing this.
Looks like directly in the iframe there is a reference to a relative path to:
3.bundle.js which for some reason in firefox add’s it to my head element causing a 404.
It seems like chrome is clever enough to ignore this but firefox appends to the
Github issue I made: https://github.com/preactjs/preact-cli/issues/1378
Please can this bundle use an absolute path, or, just remove it as looks to be 301ing to nowhere anyway???