Joseph,
You’re exactly right. The best workaround is to show the Chatter component in an iframe in a template component. You can see an example of how to do that on this post. We don’t currently have this bug scheduled for a particular release since we’re still investigating how to fix it, but we’ll let you know once a future release contains a fix
