Mario Pietsch


@Jermolene -- This PR is related to: **implement dynamic config and check for max-widget-tree-depth recursion detection** #8147 -- But it only implements the button in button protection, which as a...

>At: https://github.com/Jermolene/TiddlyWiki5/pull/8147#issuecomment-2058874825 you wrote > >That makes me wonder if an alternate approach might not be to simply suppress rendering nested button widgets? The HTML spec [is clear](https://html.spec.whatwg.org/multipage/form-elements.html#the-button-element) that interactive...

>It would be a widget that is generating a element instead of a element. The event handlers etc would continue to work as before. But we would be back at...

>I think I specifically asked about this point in the other thread. As I understood it, the theory was that it was the fact that button elements that were being...

@Jermolene - I did update the PR. It now allows 1 button in button. But as soon as the nesting goes 3 levels deep, there will be an error message....

So how deep will you go? 1000 will crash TD. My suggestion was 50 nested widgets in buttons. I doubt anyone will need more than 50 nested widgets inside a...


You are right. Let's focus on the recursion problem first.

New and simpler code with the same problem described here. It breaks the preview section, which is not updated anymore even if the text is changed. See screenshot ``` {{{}}}...