Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

causes ReferenceError in chrome 38 #30

Closed
jarofghosts opened this issue Jul 19, 2014 · 5 comments
Closed

causes ReferenceError in chrome 38 #30

jarofghosts opened this issue Jul 19, 2014 · 5 comments

Comments

@jarofghosts
Copy link
Contributor

using as part of browserify-zlib.

inftrees.js L170 Uncaught ReferenceError: Invalid left-hand side expression in prefix operation,

reproduce by simply creating an index.js

var zlib = require('zlib')

and
browserify -d index.js > bundle.js

drop the script tag into html and load the page

jarofghosts added a commit to jarofghosts/pako that referenced this issue Jul 19, 2014
@puzrin
Copy link
Member

puzrin commented Jul 19, 2014

Is it in all browsers or one specific? A bit strange that nobody reported yet.

@puzrin
Copy link
Member

puzrin commented Jul 19, 2014

See gruntfile. All major browsers run some primitive tests.

I don't reject to merge, just try to understand how could this happen.

@jarofghosts
Copy link
Contributor Author

It seems it's only happening in Chrome Canary

@puzrin
Copy link
Member

puzrin commented Jul 19, 2014

The same reported in jszip tracker Stuk/jszip#156

@jarofghosts jarofghosts changed the title causes ReferenceError in chrome 36 causes ReferenceError in chrome 38 Jul 19, 2014
puzrin pushed a commit that referenced this issue Jul 19, 2014
fix reference error issue #30
@puzrin
Copy link
Member

puzrin commented Jul 19, 2014

Released with this fix. Thanks.

But note, that browser beta versions can have any bugs, and usually nobody test/support those. If you have time - report this bug to chrome tracker.

@puzrin puzrin closed this as completed Jul 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants