@ecbos_ If multiple custom elements depend on the same CSS, you end up doing duplicate work. With a module, you only do it once.
@b1tr0t @firt @mathias No manifest icons, that’s still correct, but here’s https://t.co/jCYCTbkfYa asking @webkit to implement it. Apple icons technically are specified as <link>s, not <meta>s: https://t.co/obuewFg9aJ.
@Paul_Kinlan @gregwhitworth @DasSurma @jaffathecake @kosamari @harleenkbatra 2013, yes. See developers.google.com/web/shows/cds.
/me takes mental note to start a PR to add the missing past other CDSs.
@othermaciej @nickshanks @LucasExqDit @googlechrome @firefox Never received a single notification prompt on iOS Safari, I’d say the restriction is pretty effective! 😜
Everyone else fixing their implementation is @webkit’s chance to get it right ev
@ecbos_ Not sure what is meant by that either, but it’s definitely not an elegant way to import CSS for your custom element.
The performance win is around the lower parsing cost and reduced memory overhead compared to CSS in template strings.
The Web Almanac’s Progressive Web App chapter is now complete, including all charts and diagrams (thanks@rick_viscomimi). Check it out in its full glory—and all the other chapters as wealmanac.httparchive.org/en/2019/pwaverI. I â¤ï¸ the cute illustrations!