Does SSR need to include the data-page attribute?

[MtDalPizzol]

Hi, folks.

I REALLY need SSR for a project that is absolutely draconian on performance and loading requirements. Every unnecessary character must be purged from the final HTML delivered to the client.

Trying inertia SSR out, it seems to be working fine. But there's one issue: The root element (id="app") still includes the data-page attribute, which seems unnecessary, since all the data included in this encoded JSON has already been rendered before the HTML is delivered. So, we end up with unnecessary data duplication, since the data is rendered in the HTML and also dumped into the data-page attribute, which is irrelevante on the first rendering.

New data-page will only be needed in subsequent requests, after hydration.

So, is that really necessary or could we get rid of the rendered data-page attribute on SSR?

Is there a way to workaround this or this would be a core change?