search

WICG / cq-usecases

Use cases and requirements for standardizing element queries.
Other
184 stars 24 forks source link

Sidebars and cards use case #68

Open eeeps opened 6 years ago

eeeps commented 6 years ago

https://daverupert.com/2018/04/pitfalls-of-card-uis/#responsive-collapsing https://twitter.com/davatron5000/status/982351699367968770 https://codepen.io/davatron5000/pen/zWMrNq?editors=1100

Need to think through whether this is different enough from the existing use case for inclusion in the doc, but given that we still only have one of ’em in there, I’m trying to capture any potential new ones I see out there...

eeeps commented 6 years ago

I really liked this statement of the problem, from @davatron5000:

My component should be agnostic of the viewport. Otherwise I need to code every possible layout scenario into the component.

I think this is more or less the problem that the use case in the doc now addresses, but I don't think we ever state that problem this clearly. You kind of have to work through a bunch of specifics to figure it out. Those specifics are great, but maybe we should preface them with a clear frame like this.