Hey Jacob, thanks for reporting this issue. The version of Browser Guard should now be 3.1.6, and the bug is resolved in this version.
Let us know if there are any other issues and thank you for your support!