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

IE11 Blank White Page in Development Branch #2535

Closed
stevaras opened this issue Jul 7, 2017 · 5 comments
Closed

IE11 Blank White Page in Development Branch #2535

stevaras opened this issue Jul 7, 2017 · 5 comments
Assignees
Labels
bug For issues that describe a defect or regression in the released software

Comments

@stevaras
Copy link

stevaras commented Jul 7, 2017

Expected behavior:
See the Reaction Homepage and everything.

Actual Behavior:
Get a blank white page and nothing happens.
Many debugger errors in console but not sure which ones are the important ones.
( Can't post them now because I can't copy them from a Windows Virtual Machine )

Steps to Reproduce the Behavior:
Load Reaction Development Branch in IE11

Versions
Node: 7.1.0
NPM: 5.0.4
Meteor Node: 4.8.3
Meteor NPM: 4.6.1
Reaction CLI: 0.10.0
Reaction: 1.3.0
Reaction branch: development

@spencern
Copy link
Contributor

spencern commented Jul 7, 2017

If anyone can reproduce this and provide errors that would be particularly helpful.
it's going to be tough to fix this without knowing what's causing it

@spencern spencern added bug For issues that describe a defect or regression in the released software needs-more-detail labels Jul 7, 2017
@rhenshaw56
Copy link
Contributor

@spencern this seems to be fixed by this PR. However, i noticed it had to do with IE not recognizing some arrow-functions and ES6 syntax on the current version of transliteration currently in use on the app. Importing the bundled version seems to work.

@aaronjudd
Copy link
Contributor

aaronjudd commented Jul 10, 2017

I'm thinking the bundled version might be needed for the client version (the lib/api) (that's how I had to deal with it elsewhere) but not the server side..?

@brent-hoover
Copy link
Collaborator

This problem is fixed if you use the fork that includes the code in the PR referenced above. I'm using my fork of it at "github:zenweasel/transliteration" for testing, but you could also use the authors at https://github.com/callthem-online/transliteration

@spencern
Copy link
Contributor

Fixed by #2553

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug For issues that describe a defect or regression in the released software
Projects
None yet
Development

No branches or pull requests

5 participants