- From: Robert Utasi via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Feb 2017 23:24:41 +0000
- To: public-css-archive@w3.org
I got partial answer for the reason which is: memory issues. This is the reason why chromium has 1000x1000 limit for rows/cols. **Suggestion:** To set priority for the rows based on webusage we can use this formula: rows = 10^X -> cols = 10^(6-X) this is correct and keeps 1million cells. 1million comes from 1000x1000 cells Sample: - With this formula we can make 250000rows x 4 cols grid which is still inside the 1million cells limit. - Based on row-prority when we add 1 more row, the overlarge algorythm fires and truncates the cols to 3. and so on: at 333334 rows it truncates to 2 cols. If this is acceptable by UAs it should be a usable and fast and responsive masonry with minimum javascript. On "webusage" I mean: usually we are scolling vertically but is should work as vice-versa: if we have 4 rows only, 250000columns are allowed without truncate. That is also still in the 1million limit. -- GitHub Notification of comment by hunboy Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1009#issuecomment-277847680 using your GitHub account
Received on Monday, 6 February 2017 23:24:50 UTC