{"action":"closed","issue":{"url":"https://api.github.com/repos/nodeca/pako/issues/60","labels_url":"https://api.github.com/repos/nodeca/pako/issues/60/labels{/name}","comments_url":"https://api.github.com/repos/nodeca/pako/issues/60/comments","events_url":"https://api.github.com/repos/nodeca/pako/issues/60/events","html_url":"https://github.com/nodeca/pako/issues/60","id":100547811,"number":60,"title":"Using \"window\" as a local variable inside a closure","user":{"login":"Irrelon","id":492293,"avatar_url":"https://avatars.githubusercontent.com/u/492293?v=3","gravatar_id":"","url":"https://api.github.com/users/Irrelon","html_url":"https://github.com/Irrelon","followers_url":"https://api.github.com/users/Irrelon/followers","following_url":"https://api.github.com/users/Irrelon/following{/other_user}","gists_url":"https://api.github.com/users/Irrelon/gists{/gist_id}","starred_url":"https://api.github.com/users/Irrelon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Irrelon/subscriptions","organizations_url":"https://api.github.com/users/Irrelon/orgs","repos_url":"https://api.github.com/users/Irrelon/repos","events_url":"https://api.github.com/users/Irrelon/events{/privacy}","received_events_url":"https://api.github.com/users/Irrelon/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-12T13:45:12Z","updated_at":"2015-09-13T11:24:01Z","closed_at":"2015-09-13T11:24:01Z","body":"Hey ya,\r\n\r\nI've noticed that you declare \"window\" and use it throughout the library but this interferes with the externally named global \"window\" when instrumenting code for coverage stats. I replaced \"window\" in my cloned version of the repo with the variable name \"sWindow\" (although obviously any name would do) and the library still worked but didn't interfere with code coverage either.\r\n\r\nFYI I'm using the library via browserify to compile all the project JS and modules to a single JS file for browser consumption. After that I have a qunit process running in grunt that goes over the whole thing and checks against unit tests and code coverage."}}