Make next/previous buttons more generic. Now any element with a data-intent of scroll-[next|previous] triggers the event. Plus, any ancestor with the appropriate panel class claims to be the owner parent. However, be away of performance. A too deeply nested action intent trigger will drastically slow down the application when a scroll request is fired.