@Snugug Oh my god, same here. The worst is that changing the video playback rate with @ChromeDevTools doesn’t change the separate progress bar speed that determines when you’ve “seen†the content.
RT @briankardell: New Post: Toward Responsive Elements
https://t.co/Q8qrDdlnSG
Wondering what’s up with ‘container queries’?…
Here’s an…
@alexey_rodionov @Vincent_Scheib Tracked in https://t.co/PHMn0RMQeF. What would you use this capability for?
@maddesigns Yeah, probably. See the quoted tweet for my previous response: https://t.co/pyq1RVfFgO
@JasonNeel I’d actually feature-test this to be on the completely safe side, as described here: https://t.co/pyq1RVfFgO
@hdv I do hope, else you could just wrap it in an “else†block with `prefers-reduced-data: no-preference` (after testing if the browser knows about the media feature (https://t.co/m43ppuLymY).
@rowan_m I’m intrigued to know what happens next, too, and wish I could subscribe here to find out:
[Accept] [Block]
RT @zcorpan: <img loading=”lazy”> was just merged to @htmlstandard! Excellent work by @domfarolino et al.
https://t.co/1IXFOqDh0e
@gregwhitworth My sincere condolences. What a tragic loss. 😔
Proposal:
“`css
header {
background-image: url(hi-res.jpg);
}
@​media (prefers-reduced-data: reduce) {
header {
background-image: url(low-res.jpg);
}
}
“`
In a nutshell, this makes https://t.co/lOtVdsrfxl and https://t.co/WhhqjPJV6X availab
RT @Snowden: Reporters following up on this story should look at the burning question @WashingtonPost inexplicably failed to raise: how the…