You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing a problem in angular when I navigate from route to another, basically what's happening is that components work at the first render, but then when I navigate away from current page and then return, the components in this page stop working and I believe that this related to the internal cache you use to prevent reinitialization but I'm not so sure though.
For example, to fix this issue with the new DatePicker component which was introduced recently by metronic, I had to keep generating new id for each input whenever I enter the page in order to fix this issue and force the library to consider these inputs as new elements that need to be reinitialized.
But this solution isn't working for other components like sticky for instance.
I'm facing a problem in angular when I navigate from route to another, basically what's happening is that components work at the first render, but then when I navigate away from current page and then return, the components in this page stop working and I believe that this related to the internal cache you use to prevent reinitialization but I'm not so sure though.
For example, to fix this issue with the new DatePicker component which was introduced recently by metronic, I had to keep generating new
idfor each input whenever I enter the page in order to fix this issue and force the library to consider these inputs as new elements that need to be reinitialized.But this solution isn't working for other components like
stickyfor instance.20251213-0108-47.5440215.mp4