- From: Ferdy Christant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Jan 2020 19:55:08 +0000
- To: public-css-archive@w3.org
Compliments on the proposal itself, seems incredibly well prepared. Perhaps off-topic, but I want to share my opinion on real world usage of Masonry. Whilst I don't have data, it seems to me that it has never become a mainstream layout choice, or is perhaps past its peak. I challenge the idea that Masonry is popular. I can think of reasons, one being that they are very messy and difficult for users to decipher. Row to row scanning as most people usually take in information is not effective using Masonry, as there are no rows. It may of course work as a method to show lots of things at once, as a discovery layout, i.e. the Pinterest use case. Case in point, note how major photography services do dynamic layout: (heads up, galleries may sometimes contain nudity): https://www.flickr.com/explore https://500px.com/popular https://youpic.com/explore Same applies to Google Photos, iCloud photos and Google Image search. None use Masonry. To be fair, counter example that does use it: https://unsplash.com/ I don't know what the particular name of this smart row-based auto sizing algorithm is (does anybody know?) but it looks common, in high demand, and not trivial to do with current layout techniques. My main point is not to challenge the idea of Masonry in itself, instead to challenge the priority of this particular layout versus layouts that I think are in more demand, subjective as that may be. -- GitHub Notification of comment by fchristant Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4650#issuecomment-579426250 using your GitHub account
Received on Tuesday, 28 January 2020 19:55:09 UTC