WordPress.org

Making WordPress.org

Opened 4 days ago

Last modified 3 days ago

#4508 new enhancement

Suggestion to make "make glossary" less obtrusive

Reported by: tobifjellner Owned by:
Milestone: Priority: normal
Component: Make (Get Involved) / P2 Keywords: needs-patch
Cc:

Description

The new https://wordpress.org/plugins/wporg-glossary/ is a good idea.
However, if a page on make has many matches against the glossary, it may become hard to handle the page: whenever you move the pointer over the page you almost always happen to pass over some explained term (that you almost always know very well...) and ... poff a popup blows up and you have to wait a bit before you can continue what you were doing.

Suggestion: Make the popups trigger on click and not on hover.

I've suggested the same in https://wordpress.org/support/topic/could-it-be-a-bit-less-obtrusive/ I just don't know where is the best place for this.

Change History (5)

#1 @garrett-eclipse
4 days ago

Thought: If hover is too fast and click isn't desired there's always hover-intent.

#2 @dd32
4 days ago

  • Keywords needs-patch added

We had considered using click, in combination with a few other things for accessibility, but ultimately had ruled out using click for a few different reasons that I'm not going to go into right now.

Using hoverintent style approach however makes a lot of sense here, and will mostly avoid unintentional expansions.

If there's any pages which are showing the glossary definitions particularly badly, I'd appreciate it being linked here for reference so it can be taken into account. Some glossary items have been removed if they're not as useful as could be.

#3 @tobifjellner
4 days ago

If there's any pages which are showing the glossary definitions particularly badly,
I'd appreciate it being linked here for reference so it can be taken into account.
Some glossary items have been removed if they're not as useful as could be.

@dd32 The pre-existing Polyglots glossary has some quite long "explanations", if several of them happen to match a in page, then there may be several dangerous spots in a post, where I need to, say, mark some checkboxes... See, for instance, https://make.wordpress.org/polyglots/2019/06/11/clpte-request-woobewoo-plugins/

#4 @garrett-eclipse
4 days ago

One other thing to note with the post @tobifjellner pointed out, along with the quick to popup it takes a long time to go away so you either need to click away or wait to read the content that gets hidden behind the post. When a user desires to read the content they usually stay on the word or in the tooltip so leaving the hover area might be improved by dismissing a little faster.

This ticket was mentioned in Slack in #accessibility by sergey. View the logs.


3 days ago

Note: See TracTickets for help on using tickets.