"Multiple lines of text" not wrapping in field

Anonymous
2016-09-26T18:35:10+00:00

Hi Everyone!

I created a field with the properties of "Multiple lines of text" - 6 lines actually. When a user fills out a form and enters information into the 6 line text box, the line scrolls to the right instead of wrapping to the next line. Also, when reviewing the form after submission, the "Multiple lines of text" box only shows one line and you cannot see beyond the right border of the box. To scroll to the right, you have to actually enter the edit mode. 

I'm guessing I did something wrong because I cannot imagine this would be designed to behave this way.

I'm using SharePoint O365. Here's a snippet of the properties:

Thanks, Kevin

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

22 answers

Sort by: Most helpful
  1. Anonymous
    2017-07-28T09:54:29+00:00

    Hi Kevin,

    As the original is too old, I have created a new ticket for you to continue working with the related team. Please check your mailbox provided before (jm**@sj**) for further troubleshooting.

    @JeganNataraj, the previous case is currently archived without a solution. I would share the result here once the ticket is closed. Thanks for your understanding.

    Regards,

    Ryan

    0 comments No comments
  2. Anonymous
    2017-07-28T12:28:38+00:00

    Ryan, this is a problem your engineers can easily reproduce. That email address is our farm admin, he doesn't get involved with development. All you need to do is to create a form in InfoPath and publish it following my steps I gave you months ago. You will have the data you need for escalation.  

    Can you comment on InfoPath's replacement? Obviously it is about to go away based on the last time MS released an new version.

    Thanks, Kevin

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-07-28T12:31:06+00:00

    Hi Jegan!

    I am not much of a coder when it comes to SP. I have created webparts with scripts for pages, like shutting of left navigation. But I've never added a webpart to an InfoPath form. Can you point me in the right direction to get me started?

    Much appreciated, Kevin

    0 comments No comments
  4. Anonymous
    2017-12-12T15:44:59+00:00

    After working with a MS Engineer (shout out to Dan Li!), I got it working! Here are my steps to fix this bug.

    Prep (only needs to be done once in the domain):

    1. In NOTEPAD, create a new text file and name it textarea.css. Remove the .TXT if it is there.
    2. Open the CSS file and add the following exactly as follows: textarea { white-space: pre-wrap !important; word-wrap: break-word !important; }
    3. Save the file.
    4. Go to https://xxxx.sharepoint.com/Style%20Library, create a folder named CSS
    5. Upload the textarea.css file into the new folder

    Settings every time a form is created using a textbox in a new site collection.

    1. "Site settings" > "Site Collection Administration" > "Site collection features"
      1. "SharePoint Server Publishing Infrastructure", click Activate. Will be slow!
    2. “Site Settings” > “Site Actions” > “Manage site features”
      1. “SharePoint Server Publishing”, click Activate.
    3. “Site Settings” > “Look and Feel” > “Master Page”
      1. Expand Alternate CSS URL if collapsed
      2. Select: Specify a CSS file to be used by this site and all sites that inherit from it:
      3. Enter the following into the All Channels box: /Style Library/CSS/textarea.css
      4. Check the box for: Reset all subsites to inherit this alternate CSS URL
      5. Click OK to save it.

    That's it!

    Kevin

    13 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-12-15T03:15:06+00:00

    But has the root cause been fixed? As usual Msft transfers the cost of their bugs onto paying customers. No one has time for all these ridiculous workarounds.

    6 people found this answer helpful.
    0 comments No comments