Do you have a sample for me? Currently I’m forced to use different technology (sic) but would give it a try.
LieGrue, strub > Am 19.11.2015 um 16:45 schrieb Thomas Andraschko > <[email protected]>: > > Today i did a complete test of the windowhandler and found some bugs in > e.g. IE8. > However, there is a flickering in firefox for me. In Chrome or even IE8, it > works fine. > > 2015-11-18 22:36 GMT+01:00 Mark Struberg <[email protected]>: > >> There is no flickering IF you have html5. >> >> LieGrue, >> strub >> >>> Am 17.11.2015 um 17:26 schrieb Markus Lachat <[email protected]>: >>> >>> Hi, >>> >>> The first issue is about the flickering of the screen: >>> I am wondering if I configured anything wrong. I implemented the >> specialized >>> ClientWindowConfig and override these 4 methods and each returns true >>> >>> isClientWindowStoreWindowTreeEnabledOnLinkClick >>> isClientWindowStoreWindowTreeEnabledOnAjaxRequest >>> isClientWindowStoreWindowTreeEnabledOnButtonClick >>> isClientWindowTokenizedRedirectEnabled >>> >>> All working, no destroyed viewAccessScope and so on, however I still see >> a >>> lot of flickering when navigating over a primefaces menu backed by a >>> navigation bean (responsible for the typesafe outcome). These are mainly >>> links that cause a POST with an outcome or just simple GET links. I could >>> provide a demo for this issue. >>> >>> >>> The second issue is a nice to have for better user experience: >>> It works for buttons (thank you Thomas for fixing this >>> https://issues.apache.org/jira/browse/DELTASPIKE-968) >>> But when the user scrolled down, somewhere at the bottom of a long page >> to >>> click the buttons the page seems to scroll up again, because it shows the >>> state of the html when the page was initially loaded. >>> >>> Can you somehow improve that behavior to show the state of the browser >> just >>> the moment before a link or button is clicked? >>> >>> Best regards, >>> Markus >>> >> >>
