Mat Marquis
Mat Marquis
@pamelafox: I would be frightened for you if you _could_ fully understand Android’s `position: fixed` bugs. It’s a disaster. @scottjehl: I’ll go in and split those up into separate properly-formatted...
Ah, I bet it’s the tweet “embed.” I never did, like, test that at all.
Ah, okay, thought it upped the “infinite loop” potential.
Ah—suuuper early to start talking syntax. There are a lot of technical things we have to sort out way beforehand, just to see whether there _can_ be a viable approach...
This viewport-ish behavior is, ironically enough, something that gets kinda talked in circles. How do we distill this down to a one or two line capital-R Requirement, a la http://usecases.responsiveimages.org/#requirements...
( Starting to get those requirements together in https://github.com/ResponsiveImagesCG/cq-usecases/issues/36 )
I think I’d want to keep this first pass focused on width/height—that way we can work out the _mechanism_ for container queries without needing to figure out/spec a whole mess...
These requirements, like the [respimg ones](http://usecases.responsiveimages.org/#requirements) should only be super high-level, and used for framing any implementation conversations around the feature—no syntaxes, no gritty details. For example: > The solution...
Yeah; I was talking about this with @zcorpan the other day. It’s in the works.
Absolutely, @marcoscaceres. You know we always need all the help we can get.