This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
mdGridList: unexpected tile ordering #2225
Comments
Hi again... actually, the tab behaviour is different (still problematic). I have created another issue and plunkr for it #2226 |
mdGridList has been improved for 0.9; which closed many issues.
|
Hi, I have updated the plunkr, yet the order still seems to be wrong... |
@shyndman - FYI |
I have the same problem as well. |
+1 |
This one is kind of tricky. I have to think about it for a bit. |
This was referenced Apr 26, 2015
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
we have a case where we would like to add tiles into the grid in two ways:
a) the first tile is always fixed and basically plays the role of "add new" button for the list items
b) any number of other tiles added via ng-repeat
Unfortunately it is not possible to achieve that as tiles added via ng-repeat have the scope.$parent.$index defined (unlike the others) and as a consequence, they are always put in front of the other tiles.
See this plunkr: http://plnkr.co/edit/uFFmoZMaWallf8M3PHRi?p=preview
I would suggest to allow an "order" attribute for a tile (similar to flexbox) to be able to specify desired order of the tile in the list.
BTW, we have run into similar issue with tabs (a mixture of fixed tabs + tabs created via ng-repeat)
The text was updated successfully, but these errors were encountered: