Does Webflow's Native Pagination have any compatibility issues with Finsweet CMS load attributes when working with embed codes targeting fields in collection lists?

Webflow's native pagination and Finsweet’s CMS Load attributes can conflict when used together—especially when you rely on custom embed codes inside Collection Lists that target dynamic fields.

1. Limitations of Webflow Native Pagination with Custom Embeds

• Webflow Pagination renders only the items visible on the current page.
• Each paginated subset of the Collection List is reloaded on page change, which resets the DOM.
• If you're using custom embed codes to target Webflow CMS fields (e.g., map embeds, JSON-LD markup, third-party scripts), these restart on each pagination click.
• Interactivity or init scripts tied to the field content may break or fail to reinitialize, especially if tied to page load or initial render.

2. Finsweet CMS Load + Embed Challenges

• Finsweet's CMS Load dynamically appends new CMS items to the page through ajax-like scrolling or button clicks.
• Since content is injected via JavaScript, any Webflow-native behavior (like field bindings inside custom embed code) may not execute as expected once the new items load.
• Especially problematic with custom embed fields like script tags or raw HTML if they rely on Webflow's initial DOM render.

3. Specific Compatibility Issues

• Custom embedding of script-based content (e.g., YouTube, maps, structured data) inside Collection Lists may not function properly when items are loaded via Finsweet’s system.
• Timing issues: Injected CMS items will not benefit from page onload or DOM ready events unless you manually reinitialize associated scripts after content load.
• The combination of both systems can cause duplicate IDs, inconsistent layout shifts, or unstyled default behavior unless carefully managed.

4. Workarounds and Best Practices

• Avoid using Webflow native pagination if planning to use Finsweet CMS Load for endless scroll or “load more” behavior.
• If using Finsweet’s attributes, make sure to:
• Use the fs-cmsfilter and fs-cmsload attributes properly.
• Reinitialize your custom scripts after content is loaded. This often requires a MutationObserver or a custom JavaScript function triggered in the on:load hook Finsweet provides.
• For custom embed content, consider using plain HTML Embed Widgets with dynamic binding and wrapping any script-based functionality with manually triggered JS.

Summary

Webflow’s native pagination and Finsweet’s CMS Load system are not inherently compatible—especially when using custom embeds targeting CMS fields. Use one or the other for best results, and always ensure that any dynamic content/scripts are properly re-initialized after content loads when using Finsweet.