Help

Reporting bugs and issues

Please read my Issues Agreement and then report bugs and issues on GitHub.

Support

Try the support forum at CodersClan.

Get Support

Additional resources

Unloaded media

Most layout modes (i.e masonry, fitRows) need to measure the size of each item to appropriately account for its space in the layout. Unloaded media files like images and @font-face fonts can throw off layout and cause item elements to overlap one another. Ideally, Isotope layouts should be initialized after all inner content has loaded.

Images

Inline dimensions

For images, the best method is to specify the width and height of images inline.

If you’re using a PHP-based CMS, you can use the getimagesize function.

imagesLoaded plugin

The next best solution is to use the imagesLoaded plugin included with Isotope. It’s a small plugin that finds all the images in a context, and fires a callback function once all the images have loaded.

$(window).load()

Another solution is to initialize Isotope inside $(window).load() instead of $(document).ready(). This will trigger Isotope after all the media on the page has loaded.

@font-face fonts

Both Typekit and Google WebFont Loader provide font events to control scripts based on how fonts are loaded.

Problems with CSS transforms

As the browser implementations of CSS tranforms are still a work-in-progress, they can cause buggy behavoir with other types of dynamic content.

Disabling transforms

Set transformsEnabled to false. This is an easy step to take when troubleshooting.

Getting item position

CSS transforms will break previous patterns for getting the position of an item. See the itemPositionDataEnabled option for a stop-gap.

Accessing the instance

Similar to jQuery UI, Isotope stores a instance containing properties, settings and methods with jQuery.data. You can access the instance with the 'isotope' namespace.

CSS transforms in Opera

Using CSS transforms in older versions Opera (< 12) distorts text rendering. See how to enable CSS transitions with top, left positioning.

Infinite Scroll with filtering or sorting

I recommend against using Infinite Scroll with filtering or sorting. This combination produces a unnecessarily complex user interaction that will frustrate your users. New content gets added, but part of it might be hidden. There is no way for the user to tell what gets hidden or re-arranged when Infinite Scroll adds more content. Exercise moderation with your Isotope implementation.

If you do plan on implementing Infinite Scroll with filtering or sorting (which is a bad idea), use the insert method instead of appended.

Poor type rendering in WebKit

Type rendering may appear poor in WebKit browsers like Chrome and Safari. This is because of Isotope’s activation of hardware acceleration. A solution is to add add a matching background to the item elements. See more: dropshado.ws - Resolving anti-aliasing on WebKit hardware-accelerated elements. Another solution is to disable transforms.

First item breaks Masonry layout

With Masonry layout mode If you run into an issue where you re-size the first item, and all the rest of the items no longer fit together in the grid, you most likely need to set columnWidth option. Without columnWidth set, the Masonry layout mode will use the width of the first item for the size of its columns.

Right-to-left layouts

Isotope can be modified to support right-to-left layouts for languages like Hebrew and Arabic.

See test: Right to left

You’ll need to make the following changes:

JavaScript for right-to-left support

CSS for right-to-left support

Preventing clicks on filtered items

The recommended CSS for filtering includes pointer-events: none for .isotope-hidden. Unfortunately, Opera and Internet Explorer still let click events propagate with this style in place. But you can still dismiss click events in your click handler by checking to see if the element or element’s parent is a filtered item.

See test: Unclickable filtered