3 ms·

Thanks! 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 onc

by gildas 7y ago

Thanks! 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 ago
It’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.
- gildas 7y ago
  Google uses LitElement (version 2.0.1) [1] to create the page. You can see it by typing `litElementVersions` in the JavaScript console. [1] https://github.com/Polymer/lit-element https://github.com/Polymer/lit-element
  - dmix 7y ago
    Right, of course it was their Polymer toolchain. Thanks