Resizing Windchill text boxes - Users used to be able to do it dynamically in Chrome

[jfrankovich]

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.2.14

At one time, when using Chrome based browsers, it was possible for the user to resize the text boxes (text areas) in Windchill forms, such as Change Requests. There was a small icon in the lower right corner that could be grabbed to resize the visible text area. This does not seem to be possible anymore. Is this a bug in Windchill? A bug in Chrome? Or intentional design in the Windchill code/CSS? Is there a way to change the code/CSS to enable resizing? (We do know that it can be changed temporarily by using F12 DevTools and changing the box dimensions temporarily.

[avillanueva]

I came across this recent article: https://www.ptc.com/en/support/article/CS329418?source=search

There are many places the developers could have coded the default textarea size. I am not sure specific where the customization would be but I doubt its easy to modify without effort. I would also think that each form would require modification so I do not think its a central location. If not in the CSS (DevTools should indicate the source of the size), then it would be intentional of based on some percentage of the surrounding elements. 

[cgautier]

Hello jfrankovich,

Since when are you seeing this behavior?

Any screenshot you can share?

KR,

Charles.

[jfrankovich · Accepted solution]

Charles,
Unfortunately for various reasons I can't tell you exactly when this functionality changed but I think it has been for quite a while, as in at a specific Windchill version or update. (We have been on versions of 12.1 for some time now, but I know we had it in 11,)
At one time, textareas on things like the CR Wizard could be resized from the lower right corner.

But currently they all appear without the resize symbol.

A simple change in the applied style can make it appear.

After doing a little more digging it looks like the windchill-base.css might be what is explicitly restricting this.

Regards,

John

[avillanueva]

Seems like a simple fix. Have you tried modding that CSS to change none to both? What is the impact?

[jfrankovich]

I tested it in my QA system and it seems to work perfectly. Haven’t found any unintended consequences so I will be applying it to production as well.

John