Browser Forms

Re: is it possible to alter the textarea width and height dynamically on browser enabled forms?

raminou — Fri, 20 May 2011 13:11:23 GMT

Thanks for your reply. Actually we've thought about this and we kept it for last resort. This is because the widths and heights of textareas are coming from SharePoint list for maintenance ease.

Maybe we've forgotten to mention that this a SharePoint list.

Any other suggestions are welcomed.

Re: is it possible to alter the textarea width and height dynamically on browser enabled forms?

ErnestoM — Fri, 20 May 2011 12:43:19 GMT

You can have multiple controls associated with the same node in the schema. Each of these controls can have a different size. Then just hide/show the appropriate control based on the dropdown selection. No code!

is it possible to alter the textarea width and height dynamically on browser enabled forms?

raminou — Fri, 20 May 2011 07:51:55 GMT

Hi,We have a request to change the size (width and heights) of a textarea based on values from a dropdown list. All should be browser enabled. We have tried the following:1. Alter the view.xsl to add dynamic width and heights as so:<span><xsl:attribute name=”style”>Width:<value-of select=”my:width”> …This, as expected, worked on infopath, but as soon as we published the form, infopath deleted our modifications on the xsl.2. We tried the Jquery approach based on this blog http://riteshudupak.blogspot.com/2010/09/add-jquery-to-browser-enabled-infopath.html . This approach works when loading the form, but anything related to dropdown (where my values are somehow stored) OnChange event do not fire. It seems that the Jquery could only be loaded and executed once at load time.3. Code approach not supported by browser enabled forms4. Preserve code block on xsl not supported by browser enabled forms We are as of today desperate as we tried everything we know and nothing seems to work. Our question is: is it possible to alter the textarea width and height dynamically on browser enabled forms. If yes, what would be the approach? If no, we will have to reengineer our entire solution. Thank you for your helps