Just had this issue myself, I loaded the extension from the chrome store and it seemed to work that way. Not a fix, but at least a temporary work around until a fix is made.