# Repeater overflowing width bug

**URL:** https://community.baserow.io/t/repeater-overflowing-width-bug/12598
**Category:** Technical Help
**Tags:** app-builder
**Created:** [June 25, 2026, 4:31pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598 "2026-06-25T16:31:51Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [June 25, 2026, 4:31pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/1 "2026-06-25T16:31:51Z")

</div>

### 🤖 Kuma (Baserow’s AI assistant): often the fastest way to get help. Try asking Kuma before posting here. Available to all SaaS users, and to self-hosted users with a connected AI model.

on

### Are you using our SaaS platform ([Baserow.io](http://Baserow.io)) or self-hosting Baserow?

SaaS

### What are the exact steps to reproduce this issue?

I have 2 pages with the exact same repeater. Page A (Support Services) data source filters to exclude rows that contain a list of tags, and Page B (Career Support) is set to include rows that contain any of that same list of tags. Both repeaters are set to show 20 items at a time. Both repeaters have the exact same contents and padding (the entire page was duplicated with just the data source changed).

I first noticed the issue when looking on mobile view. Page B’s repeater spills over to the right. However, upon investigation, the issue can also be seen on desktop mode when the repeater’s number of items is increased (at least for Page B). It looks like the combination of the data source filter plus the repeater’s number of items is increasing the width of the repeater contents so it’s overflowing the repeater’s width. At a minimum it’s something to do with the number of items

> **[Career Support](https://career-resources.baserow.site/career-support)**

> **[Support Services](https://career-resources.baserow.site/support-services)**

### Attach screenshots, videos, or logs that demonstrate the issue.

 ![Screenshot 2026-06-25 092338.jpg](https://community.baserow.io/uploads/default/original/2X/6/62c2c0d00c4fdbdf5b6cd9922346bdc4adaa566b.jpeg)

---

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [June 25, 2026, 4:37pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/2 "2026-06-25T16:37:59Z")

</div>

Even when I set the repeater to a very small item number (I have it set to 4 currently in the public version), when I show more repeatedly to show all of the items, it again overflows. So it apparently has to do with how many it’s showing, whether or not the repeater is set to show that many by default.

---

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [June 25, 2026, 4:45pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/3 "2026-06-25T16:45:04Z")

</div>

and this is happening when I do a search of the repeater and also hit the button to show more…

 ![image](https://community.baserow.io/uploads/default/original/2X/b/b38b4b23a98abb4a04fd7a602dbba3b0a70f3f27.png)

---

<div class="post-metadata">

### Author: ![paljort](https://community.baserow.io/user_avatar/community.baserow.io/paljort/32/4115_2.png) [@paljort](https://community.baserow.io/u/paljort)
#### Post date: [July 3, 2026, 3:31am UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/4 "2026-07-03T03:31:15Z")

</div>

hi @bgelbart - Welcome to the Baserow community!

Would you mind sharing an export of your workspace that I can import and inspect? You can email me at [tsering@baserow.io](mailto:tsering@baserow.io) and attach the export as a zip file (or provide a download link).

---

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [July 6, 2026, 6:26pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/5 "2026-07-06T18:26:23Z")

</div>

I have emailed you the export of my workspace. And, actually, both repeaters I spoke of are doing it, if I happen to be viewing the “problem” cards; Because I have different filters on both repeaters, they are both loading different cards; for the “problem” repeater, it encounters a problem card in the first 10 that are loaded; while the other one doesn’t encounter a problem card until much farther down in the load list.

I think the bug might have to do with long website text that doesn’t have a dash (-) early enough to line break before exceeding the screen size width. The ones that don’t wrap don’t have any dashes.

---

<div class="post-metadata">

### Author: ![paljort](https://community.baserow.io/user_avatar/community.baserow.io/paljort/32/4115_2.png) [@paljort](https://community.baserow.io/u/paljort)
#### Post date: [July 7, 2026, 4:15am UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/6 "2026-07-07T04:15:40Z")

</div>

@bgelbart I haven’t received your workspace export yet (not in my junk/spam either). Perhaps you forgot to attach it?

---

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [July 7, 2026, 4:15pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/7 "2026-07-07T16:15:20Z")

</div>

I checked and I did send it - to [Tsering@baserow.io](mailto:Tsering@baserow.io) and with the zip file attached. And I just emailed it again.

![image](https://community.baserow.io/uploads/default/original/2X/5/5ba97d74d4828f8a0a0d3fbebd6039fdc23a60ed.png)

---

<div class="post-metadata">

### Author: ![paljort](https://community.baserow.io/user_avatar/community.baserow.io/paljort/32/4115_2.png) [@paljort](https://community.baserow.io/u/paljort)
#### Post date: [July 8, 2026, 1:48am UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/8 "2026-07-08T01:48:50Z")

</div>

@bgelbart I still didn’t receive any attachments from you. Definitely nothing in my junk/spam folder either.

I think it’d be best if you upload it to some shared document service (e.g. dropbox) and then send me an email with a link to download it.

Please don’t forget to include the spacing issue you raised in the other thread, which will save me time so I can look at both of them at the same time.

---

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [July 8, 2026, 4:30pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/9 "2026-07-08T16:30:01Z")

</div>

Does this work?

[**Edit by team:** A link was removed from this comment.]

---

<div class="post-metadata">

### Author: ![paljort](https://community.baserow.io/user_avatar/community.baserow.io/paljort/32/4115_2.png) [@paljort](https://community.baserow.io/u/paljort)
#### Post date: [July 15, 2026, 4:35am UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/10 "2026-07-15T04:35:24Z")

</div>

Thanks for sharing the export @bgelbart - I’m guessing the attachment was stripped due to its size (~64mb).

I’ve verified this is indeed a bug. It’s [fixed in this PR](https://github.com/baserow/baserow/pull/5719) and should be included in the next release.

---

<div class="post-metadata">

### Author: ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)
#### Post date: [July 15, 2026, 3:52pm UTC](https://community.baserow.io/t/repeater-overflowing-width-bug/12598/11 "2026-07-15T15:52:34Z")

</div>

Yay! Validation. Thanks for working on this!
