This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The styling has changed for paragraphs within the text web part in Sharepoint modern pages. All paragraphs in pages that I created prior to the March software update displays with paragraph spacing. All paragraphs in pages that I have created the past week have no paragraph spacing. I know I can just make another line break between each paragraph, but should I do that? I can see that the paragraphs are properly encoded within HTML p tags and no in-line styling.
What I really need to know is whether or not this is seen as a bug, and will be addressed quickly, or is this seen by Microsoft as the new way the rich text editor will work going forward.
Is the Sharepoint modern sites text web part RTE going to act like Notepad forever, or will it go back to the expected behavior described here? If I add extra line breaks because of the messed-up style sheet, and if it then gets fixed, I will have to go back and remove them all. Do I keep working on my intranet project, or wait for this to get fixed?
UPDATE/EDIT: Please upvote a thread on the feedback tool:
https://feedbackportal.microsoft.com/feedback/idea/08ab0f6b-23e4-ed11-a81c-0022484e6a77
in response to a Microsoft Support ticket. Details in this Community thread below.
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
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.
On July 17, the issue seem to have been fixed! Spaces between paragraphs in articles are back on new posts! Finally!
***UPDATE*** : On January 22, 2024, the problem is back in our tenant! @MelissaBrenneman can you reopen the thread?
I'm not an admin, just a site owner, so I don't know when we got our last update. However, it appears to have just arrived in our tenant, since I'm in the middle of creating a set of training pages and this behavior magically appeared when I came back from lunch and created a new page - it didn't happen earlier today.
From your notes above and my testing (to confirm that I'm seeing the same thing), it appears that the CSS is applied to the text web part when it's created, because I can edit existing text web parts with the old behavior, but a new page created from that page puts the text in a web part without paragraph spacing. On that theory, I am proceeding to create pages and manually inserting blank lines between paragraphs. If this hypothesis about when the CSS is applied is correct, then these pages should still look OK when (if) Microsoft fixes this breakage.
TBH I'm hoping that they're planning to make paragraph spacing configurable and simply forgot to add the UI element to control it. Probably a vain hope...
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
We're getting the same problem as of this week, so whatever it is it looks like it's rolling out slowly.
My Microsoft Support Case number got masked above, so there seems to be an effort to keep us from contributing information on a ticket if we have the same issue. Please, everyone, open a ticket and get a Support Case number and then tell them to look at this thread.
On my case, I was told to do a network scan using some tool that took an hour to install and run. Their instructions didn't say how to answer the questions. It looked like the wrong diagnostic tool, anyway. It seemed to be oriented towards running a diagnostic on the PC, when the issue is in Sharepoint Online via Microsoft 365. I'm feeling very frustrated right now.