Comment 12 for bug 1882982

My intention for using _top is to ensure that it breaks out of the iframe (and any other frame it might be nested inside) entirely. I felt like that was the best way to get people into the full catalog and not get them trapped inside an unexpected wrapper.

Noting that it does look nicer with some judicious changes to the carousel CSS. This test page shows a carousel being pulled from the live PINES server first and from the vanilla test server second.

https://pines.georgialibraries.org/test

(The CSS changes I made locally on PINES hide the nav arrows at small window sizes, use a smaller cover image, control the cover image height rather than width for consistency, etc. I also have the carousel setting enabled to auto-progress rather than requiring clicking or manual scrolling.)