-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add SubHeader components for lists #216
Comments
Looking forward to implementing this, as I was doing some research on lists, I noticed this screenshot on the list page, which features a grey color instead of the blue one: Which color should we be using? |
@ThomasBurleson I have finished the first implementation of this component. A few questions:
|
I think if we can reproduce [with Angular Material] the demo as shown above (with colors, layout, etc) then we will have a successful demo (that uses Lists, Icons and SubHeaders). As I infer from the snapshot, we have:
BTW, I am not sure if we have implemented all the components needed to fully implement the demo shown above. |
I just reviewed the spec and it appears that the SubHeaders have a stickiness factor:
|
And, I would say yes to both your (1) and (2) questions above. |
@ThomasBurleson, awesome thank you for all of the feedback. A few questions:
...
</material-list>
<material-divider class="inset">
<material-header> Otherwise, we could do </material-list>
<material-header class="divide-top"> Which would you prefer?
|
Also, to expand on number 1 above, I think the divider is the better approach, as we will likely want to use |
Ryan, have you seen the sticky scroll header in material? It's maybe what On Sun, Sep 7, 2014 at 10:04 AM, Ryan Schmukler notifications@github.com
Max Lynch |
@mlynch Is that in the ngMaterial Toolbar component: |
@rschmukler As I think of a
|
@mlynch, @rschmukler Should we refactor the |
@ThomasBurleson what are your thoughts on the padding issue I described above? We could use css-psuedo elements to handle the divider line, but does that feel dirty to you? Also, I think the |
Not sure, this one was modeled off the polymer one and is pretty tied to On Sun, Sep 7, 2014 at 10:20 AM, Thomas Burleson notifications@github.com
Max Lynch |
@rschmukler
I will defer to your considered best approach, then we can ask @max, @adam, @ajoslin to provide feedback... psuedo-elements are cool. Regarding the |
As per flowdock discussion, we will need to update replace the element with an |
@rschmukler - Is this issue closed and feature present in 0.0.3 or is moving it to 0.0.4 correct ? |
Specifcation: SubHeaders
The text was updated successfully, but these errors were encountered: