I really like the idea of a Zurb frontend communicating with a C# backend utilizing -
InvokeScriptAsync WebView.InvokeScriptAsync method in C#.
Anyway, I noticed that transitions between Frames utilize an animation that causes a slight (yet noticeable) flicker once Zurb is loaded and the knockout model is bound.
One way to address the flicker is to explicitly pass a null NavigationTransitionInfo into the Frame.Navigate method. It controls how the transition animation runs (or in my app’s case not run) during the navigation action. Some provided by the Windows runtime API are –
- CommonNavigationTransitionInfo (roll in from the right)
- SlideNavigationTransitionInfo (slide up)
- ContinuumNavigationTransitionInfo (short zoom-in)
Another way to prevent the flicker is set your
frame.ContentTransitions = null programmatically. Or use a much cleaner way by removing the Frame.ContentTransitions element in the Xaml -