Creating an exclusion for the Security Log error check is using a band-aid solution for the actual problem. You need to fix the actual problem that is occurring and not make the errors/log entries go away. The problem is still occurring, but now you are not getting warnings/log entries that the problem is still occurring.
There are alot of issues going on with the current Google Chrome Browser version that affects anything having to do with javascript. Google is working on a solution for these issues. If the problem is only occuring in Google Chrome then most likely it is because of these known issues in the current version of Chrome. Or of course it could be that another plugin that is having issues with the new Chrome version is where the problem is coming from. BPS Pro itself does not have any issues with the current version of Chrome.
General information about how code works and is processed for website applications
In php coding as well as most if not all coding languages for website applications you are always seeing the results/text of whatever code function was processed last. So if what you are talking about is this scenario: you click something and you see a displayed message. You then click somewhere else and that displayed message goes away. What has occurred is you will always see the last functions that were processed/the last displayed messages. Let’s say you click a button and you see a displayed message. You then click anywhere else and that message goes away, but you see a new message. The new message is displaying the last function that was processed. A simple way of thinking about this is human terms is you are always seeing the past in displayed messages, cannot see the future and the present is frozen in time until you refresh your browser or click anywhere to be in the real present. Of course what you are seeing one millisecond after refreshing your Browser is then the past again and not the present.