Doesn't work when `ember-glimmer-remove-application-template-wrapper` flag is enabled.

[cibernox]

trafficstars

Using Ember canary, if the feature flag ember-glimmer-remove-application-template-wrapper is enabled when the JS boots the SSR content is not replaced, ending on a repeated page:

[rwjblue]

Awesome, thanks for reporting! The issue here is that this initializer can no longer clear the "prior boot"...

[rwjblue]

We can change that to add another mechanism to track the boundaries. For example, if we rendered the user content like this:

<script type="x/boundary" id="fastboot-start"></script>

<!-- user rendered content goes here -->

<script type="x/boundary" id="fastboot-end"></script>

You could easily imagine implementing a bit of DOM traversal to remove all the "guts" between those markers....

[cibernox]

@rwjblue I can see how to modify the initializers to remove stuff between two known nodes, but any idea how to change the rendering to add those boundary markers?

[rwjblue]

Ya it’s in fastboot package

[mike183]

I believe #569 may have caused the shoebox data to be stripped from the page.

Reason being that if you look at the page source that was actually returned from Fastboot, it contains the shoebox data, where as viewing the page source in the 'Elements' tab of Chrome's dev tools, the shoebox content appears to have disappeared.

Has anyone else experienced this?

I assume the fix would be a simple case of updating the instance initializer to ignore script tags with a type of fastboot/shoebox?

EDIT: Also worth noting that this issue affects only ember-cli-fastboot v1.1.3+