I am start using Master-detail layout with Vaadin 24.8.1 and Sporing Boot 3.5.3. Everything work ok with the exception when I added in the detail view components that user JavaScript (e.g., a d3.js) The problem is in the rendering; when I used before SplitView with css file to open and close the detail it works ok. When I migrate to Master-detail the rendering in the detail is done very lazy, so the JS component is not created in the DOM, and if I called it with the JS in the browser console I receive an error that the element does not exist. The work around is to do a pooling in JS until the element exist in the DOM. This an ugly solution but it works. Is there any way to know where the detail ends the rendering. Of course I tried with onAttach but this event is called very early, before the rendering is done.
If you’re using executeJs to trigger that JS and it’s run before the element actually exists in the DOM, then that sounds like a framework bug that we should investigate. Could you crate a ticket in the Flow repo with reproduction details?