@JohnMu Yeah, it’s on me. We’ve just migrated off DevSite, now it should be a lot easier to implement. It’s just a matter of time.
🌒 Dark mode aficionados, my #ChromeDevSummit lightning talk on dark mode has been published on YouTube: youtu.be/4rX19mqzI5k. 📺
It’s essentially the TL;DR of web.dev/prefers-color-…. 📚
@marcenglund @vaadin Note that this is exactly what the light.css / dark.css / common.css architecture does. You set the variables in light.css respectively dark.css, and use them in common.css. No JS needed.
@rob_dodson @nhoizey The core idea is to make everything dependent on the root font size (which in turn you set to 100%, so the user can choose their preferred default size in the browser settings):
“`css
body {
font-size: 100%; /* 16px by default, bu
mrdoob @tomayac @mathias I wonder if the argument of SMIL not being implemented in all major browsers still stand. groups.google.com/a/chromium.org…
@nhoizey I’m mostly making the case for _not_ setting it to anything absolute; `100%` does not change anything of course :-)
The idea is to make it relative, so you can…
“`css
@media (min-width: 768px) {
body {
font-size: 112.5%;
}
}
“`
@marcenglund @vaadin Thanks for the kind words 😊. You can actually make it completely independent from JavaScript by following the loading strategy outlined in web.dev/prefers-color-…. I love the `media` attribute on `<link rel=stylesheet>`, it’s inc

@nhoizey @simevidas @igrigorik @ppk @rob_dodson 100% of the user’s global browser font size setting, which defaults to 16px, but can be easily overridden. pic.twitter.com/XlEdEvSFgt
@slightlylate @jyasskin @kosamari @beverloo @KenjiBaheux It’s coincidence. I get these annoying DiDi SMS in Germany and was never using their app or site on an Android device, only the iOS app.
This tip by @TimvdLippe went immediately in my git config: ⤵️
(Context: twitter.com/domenic/status…) twitter.com/TimvdLippe/sta…
MylesBorins @nodejs If you want to learn more about working with ESM in @nodejs 13 feel free to check out this blog post about the current implementation and what we are still working on.
medium.com/@nodejs/announ…
rauschma Node.js 13.2.0 is out: github.com/nodejs/node/bl…
🎉 ES modules are now unflagged!
ℹ️ Details:
– ESM on Node.js2ality.com/2019/04/nodejs…oS
– Writing hybrid ESM/CommonJS packag2ality.com/2019/10/hybrid…cFux
@simevidas @igrigorik @ppk Setting the root font size to 100% is one of my favorite tips I learned from betterwebtype.com/articles/2019/….
CC: @rob_dodson regarding web.dev (I think this is the deep link: github.com/GoogleChrome/w…)
@rowan_m 🤯 We’ve been pitching PWA wrong the entire time.
Safari will soon have (textual) Async Clipboard API support. 👏
Maybe up next: `image/png` support (web.dev/image-support-…, requested here: bugs.webkit.org/show_bug.cgi?i…). twitter.com/webkit/status/…
Great post by @ericlaw on `navigator.registerProtocolHandler()`. ⤵️ twitter.com/ericlaw/status…
@marcenglund @vaadin This will catch color scheme changes, but you also need to initialize it on first load.
@mrdoob @mathias Thinking about it more, probably one should prohibit all network-involving operations to avoid tracking (onhover etc.).
@mrdoob @mathias Definitely cool!
🤔 If SVG <script> were scoped to the enclosing <svg> tags (rather than being global, as spec’ed now), could we then have scripts execute safely in an <img>?
<!— Unreachable —>
<svg […]>
<script>/* Can’t reach ou
@mathias @mrdoob @ppparshekar I wonder why anyone thought global scope for SVG <script> was a good idea: “Any functions defined within any ‘script’ element have a “global” scope across the entire current document.”-svgwg.org/svg2-draft/int…e
I’ve extended my animated SVG favicon demo app to now test SVGs with animations written in CSS, JS, and SMIL.
Turns out, CSS- and SMIL-animated favicons play fine in Firefox (😲), but neither play in Chrome.
Demo: animated-svg-favicon.glitch.me.
Screencastyoutu.be/SlesN-eGdIEtwitter.com/mrdoob/status/…
Samsa is a really impressive variable fonts explorer: axis-praxis.org/samsa/ 🔠 twitter.com/variablefonts/…
@jaffathecake There’s movement on the bug, so here’s hoping: bugs.webkit.org/show_bug.cgi?i….