On Sat, 14 Aug 2021 09:13:25 GMT, Johan Vos <j...@openjdk.org> wrote:
>> modules/javafx.web/src/main/native/Source/WebCore/page/FrameViewLayoutContext.cpp >> line 393: >> >>> 391: const Seconds layoutScheduleThreshold = 250_ms; >>> 392: m_layoutTimer.startOneShot(layoutScheduleThreshold); >>> 393: #else >> >> I presume there was some change in the imported WebKit commits that made >> this changes necessary? > > That is a good question. I believe that was actually introduced because of > JDK-8260165 (and removed in the next update by commit > ed0baf5f23aed0d8aaa72645c8e03fde56d0f0cc) > > The problem with this 250ms delay is that in case the WebView is not visible, > it's contents won't get updated until after 250ms. That is a major pain if > the WebView is used for printing only (hence not for rendering). I think it was missed during webkit update, and caused [JDK-8269067](https://bugs.openjdk.java.net/browse/JDK-8269067) : CSSFilterTest fails intermittently in Windows. Taking this change back seems like good idea. ------------- PR: https://git.openjdk.java.net/jfx/pull/603
