RFR: 8370498: Improve how Node detects whether a layout property change requires a new layout pass [v4]

[Andy Goryachev]

On Tue, 28 Oct 2025 08:25:58 GMT, Johan Vos <jvos at openjdk.org> wrote:

> That fulfills the main goal (correct rendering, perhaps after a number of pulses, leading to flickering), but it makes the second goal (top-efficiency) really hard.

I might be way off, but I wanted to ask you this:

How many pulses are needed to finish the layout?  If we ignore for a second some pathological cases when the layout process never ends causing continuous flicker, is there a safe upper limit?

What I am getting at is - what if we run more than one layout pass (`Scene::doLayoutPass`) per pulse?  In other words, if the layout is still dirty, we keep doing the layout until it's settled, without the associated re-rendering and flicker, and if it's still dirty after N cycles we print a warning (if said warning is enabled)?

What do you think?

-------------

PR Comment: https://git.openjdk.org/jfx/pull/1945#issuecomment-3457215288