"Insert SAS Code" eating program statements in IE

[Rick_SAS]

Has anyone noticed that the "Insert SAS Code" sometimes doesn't appear correct in Internet Explorer?

Case in point: This post

Under IE 11, I see only parts of the SAS code:

However, under Chrome I can see the entire message:

I recently asked an OP to repost his program because it was illegible. I just now looked in Chrome and I see that his program is fine.

[ChrisHemedinger]

I'll take a look Rick -- maybe our code formatter is misbehaving under IE 11.  The "};" combo might be tripping it up.

[Rick_SAS]

Here's irony: I can't view your complete reply in IE 11.  It gets truncated.

[ChrisHemedinger]

A ha! Great to know.  So it's not our syntax coloring piece.  I think it might be the AddThis component (the widget that allows for sharing on Twitter, LinkedIn, etc.).  I see some errors in the IE console from that.

[Rick_SAS]

Could I get an update on the status of this issue? It has become a major irritation that affects many posts in the IML community and any other posts that use DATA step arrays.

[ChrisHemedinger]

Hi @Rick_SAS- we haven't had time to resolve this yet, but I'll try to take a look in the next few days to see if removing or tweaking our AddThis component helps the situation.

[ChrisHemedinger]

@Rick_SAS Update: I performed some testing over the weekend to try to "eliminate" the cause from any of our SAS-specific scripts and behaviors on the community.  I couldn't find the cause in our content, so I've opened a track with our communities platform vendor.  They have replicated the issue and are investigating a fix.  Stay tuned.

Thanks for your attention to this issue.  Just over 20% of our visitors come to the site using IE.  We know that IE is the corporate standard for many customers and while we can recommend Chrome and Firefox for a better experience, that's often not a practical option.  We'll get this resolved.

Chris

[ChrisHemedinger]

All fixed now! Thanks for reporting it with such detail -- it made it simple to reproduce and narrow down, so we could get our vendor to fix it.