2.0.0-alpha-2 fails for IPhone+Safari/Chrome and Windows 10 + IE11 about react-to-print HOT 15 CLOSED

@Cedware after moving to 2.0.0-alpha-4 (thanks @MatthewHerbst) it seems that our users can print, but I am now seeing your Member not found issue.

Did you manage to investigate further? Seems like the issue for me is around the stylesheet although it's difficult to replicate as I can only use Browser stack to emulate IE 11. I am hoping to get some time to look into this soon, so was interested to know if you have any more info.

from react-to-print.

I'll look into the iOS Safari issues but I regret to inform this library is not going to support IE11. There is support for EDGE

from react-to-print.

from react-to-print.

I understand your pain as someone in your position. Unfortunately I only have so much time to invest. If you happen to find any clues in solving the issues or a PR to offer up I'd be more than happy to accept

from react-to-print.

For sure, I understand time constraints and having to draw a line in the sand somewhere.

If I find something useful for IE11, I'll let you know and/or submit a pull request. However, I think the path of least resistance on my end is going to be to make a screen visible page that is formatted for print (all site specific headers and footers removed) so that the native browser printing works.

from react-to-print.

Good news, I found a fix. Will send a PR later today for your review. Thanks again for the cool project. :-)

from react-to-print.

I tried pushing a /bugfix/v2-ie11 branch, but received a permission error. I think I need permission to do so.

from react-to-print.

@SDShooter You will first need to fork the repo. Make the changes there and then submit a PR to this repo

from react-to-print.

Published your fix in the latest version. If you have any other solutions I'd be happy to accept them

from react-to-print.

Cool, thanks. I'll see if I can get around the IOS issue, but early signs pointed at an underlying issue with @media print selector not being applied properly on IOS. Will see if I can track down more info or a workaround.

from react-to-print.

Hello,
I'm still having Problems on IE11 with 2.0.0-alpha-3.
I'm receiving the error message.

Member not found

@SDShooter did you have the same Exception or is it a different problem?
Maybe I'll have a look at this problem later.

from react-to-print.

Hi @Cedware,

The issue I experienced in IE11 was a stack overflow that hung/crashed the browser due to an event handling issue.

from react-to-print.

@SDShooter thanks for your IE 11 support (I have the similar corporate overlords), but I am still having an issue with IE 11.

I have commented on this issue #49 as I came across it first. Is it related to the issue you're having?

from react-to-print.

@Cedware after moving to 2.0.0-alpha-4 (thanks @MatthewHerbst) it seems that our users can print, but I am now seeing your Member not found issue.

Did you manage to investigate further? Seems like the issue for me is around the stylesheet although it's difficult to replicate as I can only use Browser stack to emulate IE 11. I am hoping to get some time to look into this soon, so was interested to know if you have any more info.

I got the Member not found issue too. Somehow, if one of your STYLE has an animation "transform" property, you get the message. e.g. Using create-react-app + react-to-print + babel-polyfill the included app.css has this
@keyframes App-logo-spin { from { transform: rotate(0deg); } to { transform: rotate(360deg); } }
the part where cssRules[x].cssText is copied to cssStyles abend because IE11 does not get the cssText above. hence Member not found.

from react-to-print.

Going to close this in favor of #75 since that handles what seems to be the remaining issue here. Please let me know to re-open it if there are other unresolved issues.

from react-to-print.