Jaume Sanchez

That's great news! I've been waiting for panels support for a while, since this conversation on twitter https://twitter.com/jryans/status/798566112841478144 The extension needs a bit of an update. I've learnt a lot...

It could probably be easily adjusted to work with the Web Extensions API (some objects don't have the same in FF and Chrome). Since the new version of the extension...

There's been discussions to make an open-source shader editor based on Web Extensions a common tool for the different browsers. I'd love to work on that, I simply don't have...

It´s not a bug really. Three.js now uses WebGL2 by default, and rStats doesn´t instrument the WebGL2 rendering context. I'll have to update the code.

https://github.com/mrdoob/three.js/wiki/Migration-Guide#r117--r118 "WebGLRenderer automatically creates a WebGL 2 rendering context now (and fallbacks to WebGL 1 if necessary). If your project can only use WebGL 1, you can use WebGL1Renderer."

I've added support for eval and inline scripts https://github.com/spite/coverage-ext/commit/3c170828507f51b7d58f4d6a350e025306adabf3 but at this point what I'm having trouble is understanding what the instrumenting code actually does and expects the extension to...

Thanks, John. I'm working on a new version with support for the new maps services, and a few fixes. I'll add your fix as soon as possible.

That would be great. I know i did a bit of fudging with the numbers to get something on screen, and usually DoubleSide is a smell when doing geometries.

Try https://github.com/spite/PanomNom.js/

Good points. I've updated the lib so it fixes the full document layout (fixing overflow and setting height) I still think there should be an easier way to fix it....