Make WordPress Core

Opened 4 years ago

Closed 5 months ago

#41428 closed defect (bug) (worksforme)

Editor: long URLs are not broken in notifications

Reported by: eliorivero Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.8
Component: Editor Keywords: close
Focuses: ui, administration Cc:


I have Google Fonts blocked in /etc/hosts and I get this notification when I edit a post, which is fine, except by the fact that it overflows:


The attached patch solves this by allowing to break the long string and it looks like this:


Attachments (1)

41428.diff (349 bytes) - added by eliorivero 4 years ago.
Allow to break long text strings in TinyMCE notifications

Download all attachments as: .zip

Change History (10)

4 years ago

Allow to break long text strings in TinyMCE notifications

#1 @melchoyce
4 years ago

Could we potentially also style these to match other core notifications, either right above the editor or inline? (Though maybe that doesn't matter so much because of Gutenberg. Pinging @joen for any thoughts there.)

#2 @Joen
4 years ago

We're still using TinyMCE in Gutenberg. We use it to power almost every textfield. So if this is a notification that is generated by Tiny, it'll still show up. Might be worth looping in @afraithe?

This ticket was mentioned in Slack in #core-tinymce by afraithe. View the logs.

4 years ago

#4 @eliorivero
4 years ago

@Joen this notification is not showing up in Gutenberg.

#5 @ocean90
3 years ago

  • Keywords needs-patch good-first-bug added
  • Milestone changed from Awaiting Review to Future Release
  • Version changed from 4.9 to 4.8

Related: #40893

#6 @dmsnell
3 years ago

It appears like this has been fixed in Gutenberg but still remains an issue outside of there. Is there any reason not to accept this patch and fix the remaining cases? @melchoyce

@afercia has the internal issue from TinyMCE been resolved that was mentioned in Slack?

#7 @afercia
3 years ago

@dmsnell I have no idea :) Best person to ask to: @azaozz I guess.

#8 @azaozz
3 years ago

  • Keywords close added; needs-patch good-first-bug removed

@dmsnell this was fixed upstream some time ago in TinyMCE 4.6.6, see https://github.com/tinymce/tinymce/blob/master/changelog.txt#L102. I can't reproduce it in trunk and 4.9, where did you see these warnings?

#9 @noisysocks
5 months ago

  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.