The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

 Co-authored-by: jasmussen < joen@git.wordpress.org > Co-authored-by: mirka < 0mirka00@git.wordpress.org > Co-authored-by: t-hamano < wildworks@git.wordpress.org >

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook .

this is something you should use when you specifically want good typography over speed.

For me that choice is trivially easy : typography :)

But that assumes that the speed choice is as small in impact as I have perceived it to be on all the websites that already apply this. That is, negligible. But admittedly, that's a data point of 1 person not looking too deeply, and running a fast laptop. I wonder is there any way we can find out more about this performance hit? I added it to this component based on a specific suggestion .

Are there any specific parts of the UI where we want to see pretty text-wrap (i.e. "choose beauty over speed")? Or do we really want to choose beauty over speed everywhere for everybody? It may be better to start with more specific parts of the UI.

Personally I'd like to see this applied to any place where we a paragraph longer than a single line is applied. I recognize that's pretty broad, but intentionally so. But that would include:

• Descriptions in the inspector, or the dark material sidebar on the left.
• Text pages in WordPress, such as the About page, privacy policy, all the other major sections.
• Settings pages.
• Content inside modals.

I could find and confirm these tests results , where the render time difference is negligible even with a simulated 6x CPU slowdown. Also, the description of the algorithm seems to say that we won't see much of a performance hit on instances that wouldn't benefit from the better breaking algorithm.

Another good thing is that if we ever have to revert, I think we could get away with it without calling it a breaking change.

So I think I'm ok with trying it out as a blanket style on Text , once we update the snapshots and add a changelog 👍

If you're okay with this one, I could use a ✅

Thanks so much for the help 🙏