-
Notifications
You must be signed in to change notification settings - Fork 13
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
Pain Management Summary not working in IE 10 or IE 11. #17
Comments
Hi @senorpatricio -- we did not target IE 10 or IE 11 during Pain Management Summary development. It currently works on Microsoft Edge, Google Chrome, Mozilla Firefox, and Mac Safari browsers. Support for IE 10 would be difficult as IE 10 reached end of life Jan 12, 2016. Support for IE 11 is likely possible, but note that IE 11 will reach its end of life on November 30. Based on two commits in a forked version of the Pain Management Summary (commit 1, commit2), it looks like you might be able to achieve IE 11 support by:
Please note, however, that I have not tested these changes; I'm only suggesting them based on what I found in commits of a forked project that does appear to target IE 11. |
Thank you for your response and explanation. I figured it would not be targeted during development as both of those browsers are very old. I have tested what you have suggested from the forked version without any luck. I'll have to go a different route I believe. Thanks! |
I've just been reminded that we did confirm it working in IE 11 at one point (back in 2018) in order to support the pilot on an Epic system. Since then, we've upgraded it to support FHIR R4, which required us to "un-eject" react-create-app, upgrade the fhirclient lib (and other libs), and make other changes to the code. It seems that perhaps in those updates, compatibility with IE 11 was lost. |
In development and in a production environment I am not able to get this working. It's almost like the app is not seen at all when I navigate from the smart app launcher. I have included a polyfill to account for the newer methods being used (map, Object.assign, etc) but it does not seem to affect the behavior of the app.
Have you had to do anything to make it work with IE10-11?
The text was updated successfully, but these errors were encountered: