Yes, that's a well-known problem we have. It's related to the way Twitter website is loaded in browser. We have talked about it here: https://github.com/raicem/impulse-blocker/issues/33