Prevent conflicting content scripts in updates #42

neocotic opened this Issue Oct 10, 2011 · 1 comment


None yet

1 participant


Currently the guard used in content.js prevents updated versions from being able to inject their code. A simple solution is the get the current version of the extension and use that in the attribute name injected in to the <body> element.

@neocotic neocotic was assigned Oct 10, 2011

Fix delivered and functionally tested.

@neocotic neocotic closed this Oct 10, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment