Eli Grey
I think we should improve support for `AbortController` to better fix this. @bencmbrook I'll have a look at this & review your PR today
@dsamarin is this safe to merge? 👀
> I am pretty convinced this falls under undetectable, at least as far as Modernizr is concerned. I wrote hotlink.js 5 years ago, before blobs and object URLs were a...
@patrickkettner I looked into it, and it seems like this is correct. If the browser doesn't support URL.createObjectURL and the Blob constructor, then it already doesn't support noreferrer in the...
@patrickkettner Why is this issue still closed? Edit: Thanks for re-opening.
Read [hotlink.js#L144-L164](https://github.com/eligrey/hotlink.js/blob/63c94dd5dd7d16d41b2b5ef4c91208ce7d8d3893/hotlink.js#L144-L160) and [hotlink.js#L108-L120](https://github.com/eligrey/hotlink.js/blob/63c94dd5dd7d16d41b2b5ef4c91208ce7d8d3893/hotlink.js#L108-L120) to see how I implemented detection for this.
Do other browsers also restrict PerformanceServerTiming and PerformanceResourceTiming properties in a similar manner?
Assuming that openDB is implemented correctly, I would guess that `console.log('TEST', value);` may be causing a memory leak.
Webpack 5 might be able to solve this issue with its recently added [native Worker support](https://webpack.js.org/blog/2020-10-10-webpack-5-release/#native-worker-support).
@bbrown-extensis Should this issue be closed?