Really informative HTTP203 episode on cross-origin fetches now and then with @DasSurma and @jaffathecake ⤵ï¸. Recommended background reading: https://t.co/0YjqEikDVa by @mikewest. https://t.co/MVRVFROCs4
@jonalvarezz Woohoo, happy it works. 🎉
Next challenge: add a toggle: https://t.co/FKfxCMMVoL.
RT @ChromiumDev: Chrome 81 is rolling out now! Shooting from his apartment, @petele has all the details on app icon badging, hit testing fo…
RT @j9t: The Web Development Glossary is now: available 🚀
* 1,945 terms and abbreviations
* 2,002 explanations and definitions
* 245 pages…
@jonalvarezz There are media types (https://t.co/DDLFIWP8lL) and media features (https://t.co/35pOthlFwv). You’re dealing with a media feature. Each media feature expression must be surrounded by parentheses (https://t.co/rGb0m87vT1).
@sw12 Favorite related post: https://t.co/MMIw2X0MAb.
@catalinred @davidbaron True, but then they still need the JavaScript handler for the fallback… :-)
@davidbaron It works (https://t.co/SWB8gZMJVx), but I guess they need to target some older browsers that don’t yet support SVG favicons.
@crswll You can relatively easily find out: https://t.co/WefCDFgM7H.
@crswll Looks like it’s indeed not working. Looking at its compatibility info in the App Store, they seem to support down to iOS 10, probably that’s the reason. Apps compiled against iOS 13 support it for sudeveloper.apple.com/ios/submit/12s3).