RT @polymer: 🔖💀 Edge is starting a new chapter tomorrow! 🎉
🔠@straversi1 shows you how you can take advantage of its new WCs APIs to autho…
@firt @scottjehl Something that `env()` should cater for: https://t.co/lywlS0Lo7B. Now being standardized: https://t.co/FqOldKi4iA.
@reillyeon 🚌 Bus lanes to the rescue, established 1963 in Hamburg: https://t.co/TqUKK7TrwA. #TIL
RT @Log3overLog2: Chrome plans to phase out support for third-party cookies. “Our intention is to do this within two years.”
https://t.co/…
@yoavweiss @DasSurma This is a pretty good thread: https://t.co/8J3MNnemfD.
@bogas04 @styfle @rmondello @DasSurma @vexii12 @intenttoship @w3c @polyfillio This is something we have brought up in https://t.co/otH38QSd7T. Feel free to chime in with additional use cases. Thanks!
@tcurdt I guess that’s an adequate summary :-)
The final puzzle piece of dark mode 🌒 support in Chrome comes together: we’ve just sent the Intent to Ship email for the CSS `color-scheme` property and meta tag: https://t.co/lAhydN6Ep7. Here’s what it does: https://t.co/C1VDVnaCti.
Oops, correct link: https://t.co/wUXaodstqH.
Intent to deprecate and freeze the Chrome user-agent string in HTTP request headers as well as in `navigator.userAgent`: https://t.co/2UPIRhxTUE.
@co60ca @ChromiumDev @petele The thing is, the current (no opt-in) work-around (playing an invisible video) is worse for many reasons and has the same effect as a `”screen”` wake lock, so we made `”screen”` no opt-in, too. Note, though, that the story is