Will boost page load performance.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | masonry-1939114-4-use-behaviours.patch | 5.04 KB | gapple |
| #1 | masonry-use-js-behaviors-1054616-0.patch | 5.02 KB | ih2502mk |
Will boost page load performance.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | masonry-1939114-4-use-behaviours.patch | 5.04 KB | gapple |
| #1 | masonry-use-js-behaviors-1054616-0.patch | 5.02 KB | ih2502mk |
Comments
Comment #1
ih2502mk commentedNot sure if it will give that amount of increase to page load speed, but it definitely will improve developer experience. Because I've been scratching the back of my had trying to guess, how masonry gets attached to the view if there is no js in this module.
A patch adds a js file to masonry_views submodule and changes the way options are transferred to javascript (i.e. use Drupal.settings).
I would suggest the author of this project to reach out to author of views_fluidgrid project to join forces.
Comment #2
gappleMarked #1933200: Not getting re-applied after AJAX sort? as a duplicate, since Masonry seems to be correctly applied after an AJAX update to a view with this patch applied.
Comment #3
gappleMarked #1961986: Exposed filters as a duplicate
Comment #4
gappleUpdated patch against 7.x-1.x-dev
Also includes small selector change that should address #1942400: Views field view ( view in view) also get masonry item property
Comment #5
Anonymous (not verified) commentedThe upcoming 2.x version of Masonry uses an external file instead of inline javascript, so that should address this issue.
Comment #7
dobe commentedHmm. Maybe I shouldn't reopen this but I am running into an issue that is similar to this problem. When using views ajax. The new content does not get the .masonry-brick or the attached style to the items. So it just overlaps everything and sits on the left side.
I am using masonry api 2.0 and masonry_views 1.0.
jquery 1.7
Is there something I am missing here?
Thanks in advance.
-Jesse
Comment #8
dom. commentedThis issue has been commited to 2.x years ago.
(Closed as part of clean up by new maintainer).