myownstandard

> It always happens on the start up of the App, should work correctly after few seconds. > It's an issue about the lazy-loading mechanism. Not quite like that, cause...

> @myownstandard Humm, it depends on the usage pattern. In my case, clicking-in to that content and back could always solve the issue. > It's very likely that the content...