-
Notifications
You must be signed in to change notification settings - Fork 47.7k
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
Minified version broken in IE8 #2247
Comments
What encoding are you serving your HTML with? My guess is if you add |
Never mind, I see that the character is actually missing. Maybe a bug in uglifyjs? |
@spicyj As it's encoded the charset is irrelevant unless uglifyjs decodes it, being zero-width/invisible I imagine it would look like nothing is there... but it really seems like nothing is there. Very weird. |
https://github.com/mishoo/UglifyJS2/blob/master/lib/parse.js#L209 Is apparently the culprit, but it doesn't seem like it should be. Perhaps uglifyjs decodes strings first and then strips for some reason... |
Hmm, this is interesting, this problem only surfaces if you double-uglify the source, perhaps something is wrong in our build-process? |
PR #2249 |
@cascadian I should add; if this is a priority for you simply replace |
Yes, we double uglify to remove dead requires from the tree (see #1933). |
Is this still an issue? I'm seeing it with react-with-addons.min.js v 0.12.2 in IE8. |
Ping, this is resolved in uglifyjs/master now at least. React should go the way of #2340 if you ask me though. |
This issue, although easily fixed by @syranide's DIY patch, still exists in http://fb.me/react-0.13.1.min.js and any other FB-packaged react.min.js. :| Sorry to be a nag. In the end this is all IE8's fault anyway. |
@markplindsay I haven't verified, but this was fixed upstream in UglifyJS some time ago so it should have solved itself... @zpao is it possible you're running the build process with an older UglifyJS? |
@syranide, thanks for your followup. I am looking at a react-0.13.1.min.js I wgot from http://fb.me/react-0.13.1.min.js. Changing |
@zpao Ah, apparently we've locked the uglifyjs dependency to |
We just got bit by this issue. Please update uglify! |
AFAIK no reason not to upgrade. @syranide want to send a PR to the 0.13-stable branch? (I forget how to update shrinkwrap files properly though…) |
Send to master and I'll pull it in with other things cheers, On Apr 10, 2015, at 12:26 PM, Ben Alpert <[email protected]mailto:[email protected]> wrote: AFAIK no reason not to upgrade. @syranidehttps://github.com/syranide want to send a PR to the 0.13-stable branch? (I forget how to update shrinkwrap files properly though…) — |
Apparently we needed to get to v2.4.17 to get the fix for facebook#2247. We shrinkwrapped on the same day but the timing didn't work out so we missed it.
Just confirmed that this is correct in the minified build now. We'll ship 0.13.2 this week with the fix. |
will 0.12.x get rebuild too? |
@ledowong No, we don't generally do point releases except for the newest minor release except in the case of a security vulnerability. You can patch in the change locally and make your own build of 0.12 if you're unable to upgrade to 0.13. |
line 66 of setInnerHTML
node.innerHTML = '\uFEFF' + html;
is minified ase.innerHTML = "" + t;
in react.min.js and react-with-addons.min.js. An exception is thrown on on line 71 becausetextNode.data
isundefined
.Here's a repro that's modified from the basic example
The text was updated successfully, but these errors were encountered: