Do you have a GitHub issue / link for that?
There are no errors in the console, but I can still see the "ps" classes being added to the side menu
According to https://support.abp.io/QA/Questions/6953/Lepton-X-scrollbar-not-visible-in-Blazor, the perfect scrollbar should have been removed from Blazor UI because of the mentioned issues. We already upgraded to ABP v8.1, and while this seems to work for the main content (we can see the native scrollbar), the side menu still has the buggy "perfect" scrollbar. Is this a bug? When is this going to be fixed? Is there a workaround for that?
Unfortunately, the old question was already closed and we couldn't respond to it. But since it's a follow-up question, I would like to ask you to refund the current question, thanks.
Thanks, is there already an estimate for 8.2 release?
Hi,
thank you for your reply, although it doesn't really answer the question.
Even though we might get a proper logout working, and the user can at any time refresh the page - why should (s)he?!
We don't see it as good user experience to just trigger a logout every 30mins. That's not how websites should behave nowadays.
So is there any reason why the template doesn't do a refresh token flow and why we shouldn't? Or is it just not implemented yet?
Other Framework also refresh it in the background. Like Duende BFF uses AccessTokenManagement. Here is the RefreshUserAccessToken in Duende, for example https://github.com/DuendeSoftware/Duende.AccessTokenManagement/blob/2a6d0a60a564a590ee4f0c87c08e8406eb753e88/src/Duende.AccessTokenManagement.OpenIdConnect/UserAccessTokenManagementService.cs#L145
Is there a reason why the Blazor Server template does not use the standard OpenId refresh token flow to obtain new Access Tokens?
