Sebastian Helzle

Hi @grebaldi thx for the review! This morning while walking the 🦮 I thought about batch loading the nodes in the UI as a future optimisation. Meaning instead of loading...

@bwaidelich what do you think, should we merge this change and open a follow up to rework the ui loading state for 8.4 f.e.? Or combine both into 8.4 to...

Sadly some additional tests in a large page in a real page with almost 300 nodes make the usability worse, as the async request takes 3-4s. I don't unterstand right...

I did some further modifications by removing duplicate node context paths (which the tested page had a lot of) and I created a separate branch with further optimisations which include...

@mhsdesign are we finished here now? I merge the current 8.3 and the node updates on click disappeared again thx to Wilhelms fix.

@grebaldi @mhsdesign one thing this PR changes is that rendering the page content will not update the stored nodes anymore with the state from the rendered nodedata. It relies on...

@grebaldi @mhsdesign I removed some code in the content tree document change saga and this way the content tree always reloads the nodes and this way we have up-to-date content....

Hi @laurahaenel, what is the state of this PR? I recently helped two people again who had problems with the loading indicator due to Fusion issues and I thought about...

Ok. Either way, I think we also need a timeout to help with debugging. So if the iframe doesn't load in a certain time and doesn't trigger our event, I...

@mhsdesign why did you reopen the issue? We can archive https://github.com/neos/twitter-bootstrap I guess. I'm not aware of other dependencies