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 have found a workaround. Find a page created before this issue started (march 23?) and "copy to" your desired location. That copy seems to retain the correct paragraph spacing even after publishing it. The suggestion in the other comment to create a new page from settings>add page> template does work initially but you lose the correct paragraph spacing after the page is published. When copying an older page it seems to be able to retain it somehow. Hope this is helpful!!
I am just now experiencing this issue with the creation of new site pages. In addition to the paragraphing issues my headers 2 and 3 seem to be acting very strange! They are not going to the correct font size and I cant do things like bold them. (very frustrating!!)
![](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(121.6, 78%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Leave it to Msft to create such a confusing mess that users have to navigate - no other software company would release a solution that functions differently depending on when a page is created. The rte has always been flawed - we had a lot of complaints about double line breaks when users hit enter, and being unable to fix that. The "old" solution was to tell them to use the Word trick (shift + enter) to add a single line break and my guess is this "fix" was supposed to address that double line break issue. Now I have to tell them they have to do that twice to get a new paragraph? Ridiculous - and don't hold your breath for a real fix.
Hi John,
that style difference you've found is interesting. I have a case open in Microsoft support, let's see if they are able to speed up the fix for this issue.