topic Re: Insert code boxes appear to be eating closing braces in All Things Community

Insert code boxes appear to be eating closing braces

ballardw — Thu, 18 Feb 2016 15:12:54 GMT

It appears that one of the insert code options is removing trailing } in code.

One example in https://communities.sas.com/t5/Base-SAS-Programming/Shifting-Values-Left-Across-Variables/m-p/250809

in the posts by DanZ and RW9.

Re: Insert code boxes appear to be eating closing braces

RW9 — Thu, 18 Feb 2016 15:26:37 GMT

Could you screenshot an example, as it looks ok to me?

Re: Insert code boxes appear to be eating closing braces

ballardw — Thu, 18 Feb 2016 17:57:13 GMT

Re: Insert code boxes appear to be eating closing braces

Reeza — Thu, 18 Feb 2016 18:25:55 GMT

Looks fine to me...

Looks okay to me. I'm on Chrome

Re: Insert code boxes appear to be eating closing braces

ballardw — Thu, 18 Feb 2016 18:45:13 GMT

So we have yet another reason not to use Internet Explorer. But at work I don't have a choice.

Re: Insert code boxes appear to be eating closing braces

ballardw — Fri, 19 Feb 2016 04:12:35 GMT

Using Firefox from home the posts appear correct. So this seems to be basically an Internet Explorer issue.

Re: Insert code boxes appear to be eating closing braces

RW9 — Fri, 19 Feb 2016 09:14:08 GMT

Ah, your using IE, think we have isolated the problem. You do have a choice, just go on strike until they provide working tools 🐵

Re: Insert code boxes appear to be eating closing braces

Rick_SAS — Wed, 24 Feb 2016 15:09:55 GMT

This appears to be the same problem that I reported two weeks ago in

https://communities.sas.com/t5/Community-Matters/quot-Insert-SAS-Code-quot-eating-program-statements-in-IE/m-p/249956#M1393

On IE, the code gets truncated. It appears that the opening brace (??) might be a trigger for the problem.

I know that people are trying to be helpful, but please refrain from responding "just use Chrome." IE accounts for about 50% of the browser market. This is a serious problem that needs to be addressed by the @Community_Help.