Soon this will be only last thing with our Abp9 update. You provided way to fix one problem our self but when this update was coming SOON I decide that I will wait 9.3.7. And that solution would need tons of changes to replace all buttons with our override. So it would be really nice that you could release it as soon as possible. What is your current plan for it?
Ok nice. I will close this then.
Can support team answer this and add it to your backlog if you are willing to make this change?
I'm at half way in switching to standalone. And I have switched one part where this problem exists and standalone change didn't fix my problem. So you managed to reproduce my problem? What was reason for the problem? Something related to stopPropagation? And what was changes that you need to made to get reproduce it? Just info if there is any other way to avoid it? What is difference with abpClick and normal click when used in abp-button? How soon are you going to release next patch for 9.3?
As I said in my initial message that I tried use click and it worked as it should. Currenlty I'm trying to migrate whole project to standalone structure. ng generate changed quite well but still lot of work.
Is your application module based from the beginning from main.ts?
There is already ThemeSharedModule in module where my component is declared. Do you have other idea how can I possible handle this without changing to standalone components?
Thats all for now. Thanks. I did have problem with module based components that I have added to SettingsTabsService. It was related to not finding abpLocalization pipe. But it seems to be fixed by changing those components to standalone and providing abpLocalization to each of those components.
That "createSaasRoutes" fixed that TenantComponent problem. Should I change all abp routes to this kind?
Original problem was this sidebar was not showing 
And reason was that here was not application layout component instead empty layout component which is not containing sidebar.
So I was figuring out why there was not application layout component in use like it was before update.
