1 个回答
According to the SF development team, this is expected behavior. I can sort of understand why. If you switch away from a tab and the refresh event is raised, that tab needs to be updated in case it is displayed again.What I do NOT understand, is why this event is raised for components after the current record is navigated away from. We are hitting the 100-SOQL-query limit because of this bug. There needs to be an event that is raised when a component is removed from view or the component should be destroyed immediately.I created an Idea for this https://success.salesforce.com/ideaView?id=0873A000000E84vQAC