`data-turbo-frame="_self"` not compatible with `$dataTable->isRequestFromTurboFrame()`

[RafaelKr]

I just noticed that clicking pagination links always sends back a full html document.
Inspecting the headers shows turbo-frame: _self, so it can't determine the actual data-table frame.

This seems like an upstream bug in Turbo, but maybe we could work around this by using 'data-turbo-frame': 'kreyu_data_table_' ~ data_table.vars.name for all pagination links for now. What do you think?

Edit: It's indeed an upstream issue: hotwired/turbo#1349

[alexandre-castelain]

Hi !
I don't know if it's still a problem, but if you follow this : https://github.com/Kreyu/data-table-bundle/blob/main/docs/src/docs/features/asynchronicity.md#server-side-responses-for-turbo-frames

Even with pagination, even with data-turbo-frame="self", the serveur will only render the Datatable and not the full page.

[RafaelKr]

Hey @alexandre-castelain! We've followed exactly that pattern. And it works for search and filters.

But are you sure it works for the pagination for you? Which version and theme did you test with? We're currently on 0.32.1 with the default theme (some adjustments, but not related to pagination behavior) and clicking a pagination item sends back the full HTML. I can see it in the network tab. The request sends turbo-frame: _self as header. For search and filters it sends the correct frame id as header (turbo-frame: kreyu_data_table_employee_index).

[alexandre-castelain]

Without theme, I still have the correct result. The Turbo-Frame in the request header is the correct one and does not refer to _self.
I use the latest version of the bundle.

Can you provide a reproducer ?