WordPress.org

Make WordPress Core

Opened 6 months ago

Last modified 3 days ago

#44604 new defect (bug)

TinyMCE tooltips should persist when hovering on them

Reported by: afercia Owned by:
Milestone: 5.1 Priority: normal
Severity: normal Version:
Component: TinyMCE Keywords: needs-patch
Focuses: Cc:

Description

Related to the changes made for the Gutenberg tooltips in https://github.com/WordPress/gutenberg/pull/8033

A tooltip should persist when the mouse pointer is moved hover the tooltip itself. This is a specific WCAG requirement related to the WCAG 2.1 'Content on hover or focus' guideline: https://www.w3.org/TR/WCAG21/#content-on-hover-or-focus

Persistent The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

More details on the GitHub issue linked above.

The TinyMCE fix is coming from upstream and should be merged in core for 5.0, see conversation on Slack > #core-tinymce: https://wordpress.slack.com/archives/C0UCMQP0F/p1528130639000183

Change History (9)

#1 @pento
3 months ago

  • Milestone changed from 5.0 to 5.0.1

#2 @pento
5 weeks ago

  • Milestone changed from 5.0.1 to 5.0.2

#3 @pento
5 weeks ago

  • Milestone changed from 5.0.2 to 5.0.3

#4 @audrasjb
3 weeks ago

  • Milestone changed from 5.0.3 to 5.1

5.0.3 is going to be released in a couple of weeks. We are currently sorting the remaining tickets in the milestone. It doesn't appear that ticket can be handled in the next couple of days (still needs a patch). Let's address it in 5.1 which is coming in February. Feel free to change/ask to change the milestone if you think the issue can be quickly resolved.

#5 @pento
3 days ago

@afercia: Do you know if the fix for this landed in TinyMCE?

#6 @afercia
3 days ago

@pento unfortunately no. Waiting for a reply for #35710 too.

#7 @pento
3 days ago

Okie dokie. Is there are ticket on the TinyMCE repo for this?

#8 @afercia
3 days ago

I don't think so. Better ask the component maintainers though.

#9 @azaozz
3 days ago

Similarly to #35710 this should be fixed upstream. As TinyMCE 5.0 is out, our best bet would be to make a PR for TinyMCE 4.0.

Note: See TracTickets for help on using tickets.