[5.x]: view.registerAssetBundle('craft\\web\\assets\\admintable\\AdminTableAsset') in template causes infinite refresh loop

[dgrigg]

What happened?

Description

{% do view.registerAssetBundle('craft\web\assets\admintable\AdminTableAsset') %} in template that is referenced in the Control Panel via a template UI element (see attached) causes an infinite loop where the template is re-render infinitely ever 1 second (approximately).

If the registerAssetBundle is not added the template never refreshes. If the registerAssetBundle is called, even if the AdminTable is not used, the refreshing happens.

Steps to reproduce

1. Add a template UI element to the an Entry type and reference a template that contains the code view.registerAssetBundle('craft\\web\\assets\\admintable\\AdminTableAsset')
2. Click on one of the entry type entries in the CP to load the entry

Expected behavior

The template loads and shows the data in a table.

Actual behavior

The template is loaded and then continues to infinitely reload/refresh.

Craft CMS version

5.8.19

PHP version

8.3.28

Operating system and version

Darwin 25.1.0

Database type and version

MariaDB 10.11.6

Image driver and version

Imagick 3.8.0 (ImageMagick 7.1.2-8)

Installed plugins and versions

Plugins
Abandoned Cart 4.0.8
Amazon S3 2.2.3
Craft Commerce 5.4.9
Dumper 5.0.1
Element API 4.2.0
Elements Panel 3.0.1
Facebook Conversion v1.3.3
Feed Me 6.11.0
Linkit 5.0.1
Lists 5.0.0
Maps 5.0.4
Minify 5.0.0
Postmark 3.1.0
Ray 2.1.1
Redactor 4.2.0
Retcon 3.2.1
Retour 5.0.12
Scout 5.0.7
Sentry Logger 5.0.2
Servd Assets and Helpers 4.2.2
Sprig 3.7.1
Stripe for Craft Commerce 5.1.0.1
Upload 5.0.0

[linear]

CMS-1736

[brandonkelly]

I’m not able to reproduce that, with a template that only has the line:

{% do view.registerAssetBundle('craft\\web\\assets\\admintable\\AdminTableAsset') %}

Can you reduce your template to just that, and see if you still get the same behavior?

If not, then try bringing back other aspects of your template until you find what’s triggering it.

[dgrigg]

Ok, digging around a bit and I think I found the issue.

This is the payload returned by the call (minus some identifying info)

{
    "pagination": {
        "total": 1,
        "per_page": 10,
        "current_page": 1,
        "last_page": 1,
        "next_page_url": "?next",
        "prev_page_url": "?prev",
        "from": 1,
        "to": 1
    },
    "data": [
        {
            "id": 5756810,
            "title": "xxxxxxxxxxxxxxxx",
            "url": "https://xxxxxxxxxxxxxxxxx,
            "startDate": "5th Dec 2026",
            "endDate": "5th Dec 2026",
            "status": "Expired",
            "edition": "<div>some escaped html</div>",
            "event": "<div>more escaped html</div>",
            "organiser": "<div>and a litte more escaped html</div>"
        }
    ]
}

Playing around with the data values, the edition value is set in the controller by this edition' => Cp::elementHtml($edition) which seems to be the root cause of the looping. If I just return a string it works. This was being used in Craft 4 to create a link in the table to navigate to the related item. Any ideas?

[dgrigg]

@brandonkelly I think I found the answer Cp::elementChipHtml($edition) works fine while Cp::elementHtml($edition) causes chaos.