You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.
1.Child grids "inherit" the characteristics of the parent grid. So a 50/50 child grid will split to 33/33/33 when nested inside a 33/33/33. responsiveness is inherited as well
tried to use "JSBin" but received a 504 error when trying to access the site. I created a JS Fiddle instead: http://jsfiddle.net/KxQ8B/1/
3.Nest a "ui-grid-a" inside of a "ui-grid-b ui-responsive"
4.The parent grid should be split 33/33/33 and be responsive. The child grid should split 50/50 and NOT be responsive.
5.The parent grid splits 33/33/33 and is responsive. The child grid splits 33/33/33 and is responsive
Running on IIS 7 and VS Personal Webserver. Tested in the latest versions of Desktop Chrome, Chrome for IPad/iPhone and Mobile Safari.
7, Using JQuery 1.9.1 and JQM 1.3.1
8.I can see that it's a CSS issue.
The text was updated successfully, but these errors were encountered:
Thanks for reporting the issue. I just committed a fix.
Class ui-responsive will only affect the blocks that are immediate children. You can add the class to the nested grids if you want to make them responsive as well. See http://jsbin.com/esekic/5
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1.Child grids "inherit" the characteristics of the parent grid. So a 50/50 child grid will split to 33/33/33 when nested inside a 33/33/33. responsiveness is inherited as well
3.Nest a "ui-grid-a" inside of a "ui-grid-b ui-responsive"
4.The parent grid should be split 33/33/33 and be responsive. The child grid should split 50/50 and NOT be responsive.
5.The parent grid splits 33/33/33 and is responsive. The child grid splits 33/33/33 and is responsive
7, Using JQuery 1.9.1 and JQM 1.3.1
8.I can see that it's a CSS issue.
The text was updated successfully, but these errors were encountered: