Eric Portis

I really liked [this statement of the problem](https://twitter.com/davatron5000/status/982358746600001536), from @davatron5000: > My component should be agnostic of the viewport. Otherwise I need to code every possible layout scenario into the...

Yeah, in that case, you’d have to make a resizable wrapper, and prevent resizing directly on the textarea, like this: https://codepen.io/eeeps/pen/YQwyPz?editors=1100

Great example of a menu panel that the user can open and close, which adjusts the size of everything else on the page: https://github.com/w3c/csswg-drafts/issues/3852#issuecomment-493683805

Should this be revisited, in light of the Permissions-Policy → Document-Policy/Structured Headers changes?

Putting performance concerns aside for a minute... error behavior matching what browsers do when they currently download images which they cannot display for whatever reason – maybe adding a console.error...

@annevk screenshots of that pen (which references a FLIF resource that no browser can decode) in: Safari:  Chrome: ![Chrome shows both a broken...

@clelland that sounds right to me! --- Whether or not an image gets loaded or displayed — it would be *really* nice for authors to get some kind of hook...

Based on the explainer, it looks like instead of inverting the colors, Chrome will now display a placeholder. This feels much nicer and more practical. To make it even more...

If FLoC is communicated via client hint, and access is delegated to third parties by the first party via Feature Policy, then it's more-or-less equivalent to active fingerprinting, risk-wise: https://github.com/yoavweiss/client-hints-infrastructure...

I guess the first way to make it more transparent will be to have an answer to: what's going to determine "what kind of clustering makes sense"? What’s the ML...