Tabs are not meant to be used for super long content, or to swap between pages (in length) of content.

You might try the JS option listed here:

https://foundation.zurb.com/sites/docs/tabs.html#js-options

data-auto-focus

I thought tabs was supposed to be used as a container for contents?? No? Why limit it to only short content?

Anyway, I found a solution for that by making each tabs have their own independent scroll. It can be achieved with simple css like :

.tabs-panel{
	overflow: auto;
	height: 100vh;
}

But now I have another question. How can I integrate hammer.js with foundation tabs so it can be swiped left/right to open next tabs-panel?

I'm actually trying to build progressive web apps with foundation and laravel, and i want it to feels like native apps by using swipeable tabs.

The original issue is for actual query tabs, but it feels like the same issue, really, since it's behaving the same way in the results grid.

see: ShowBox Mobdro Vidmate