2 ms·
Thanks for your work on this and good job not having to inject JS for so long. I’m surprised there hasn’t been other nasty web stuff that required it.
by dmix 7y ago
Thanks for your work on this and good job not having to inject JS for so long.
I’m surprised there hasn’t been other nasty web stuff that required it.
- gildas 7y agoThanks! You can find web components in a lot of unexpected places. For example, this page [1] contains more than 10K web components... The good news is that once the Pandora's box is open, I had the idea to code SingleFileZ [2] which also requires JavaScript to be enabled but frankly uses it! [1] https://bugs.chromium.org/p/chromium/issues/detail?id=4 https://bugs.chromium.org/p/chromium/issues/detail?id=4 [2] https://github.com/gildas-lormeau/SingleFileZ https://github.com/gildas-lormeau/SingleFileZ
- dmix 7y agoIt’s always interesting what we volunteer ourselves to become experts in through our work in software. I respect any OSS developer that dedicates themselves to this type of thing. I’m curious what google used to create that chromium bug report page (internal framework or a custom job). The internal tools targeting devs with good browsers will always have the most advanced stuff it seems.