Skip to content

Conversation

@cpeel
Copy link
Member

@cpeel cpeel commented Dec 24, 2025

As a stepping stone to get rid of the new window JS code which has long outlived its usefulness, replace the user preferences pop-ups with tooltips. This makes the help more accessible and avoids needing to open a new window which might be blocked by pop-up blockers.

Sandbox: https://www.pgdp.org/~cpeel/c.branch/better-pophelp/

@cpeel cpeel self-assigned this Dec 24, 2025
@cpeel cpeel force-pushed the better-pophelp branch 2 times, most recently from c239c4e to 5cacaea Compare December 24, 2025 08:00
output_tab_bar($tabs, $selected_tab, "tab", "origin=" . urlencode($origin));

echo "<p>" . _("Click the ? for help on that specific preference.") . "</p>";
echo "<p>" . _("Hover over a setting to get more information about it.") . "</p>";
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hover may be hard to understand in the context of a touch device. Also, to me at least, the hover behavior was a little obtrusive navigating around my user preferences. Probably wouldn't think twice about it unless observing the behavioral differences though.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried it on my (Android) phone. Press-and-hold worked just fine. On my iPads (2017 and 2024), press-and-hold does not work. Turned out that just a quick tap did work for the iPads. I don't have an iPhone to be able to tell what works on them.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's not ideal but I couldn't come up with a better way that made them accessible without being obtrusive. One of the reasons I put them over the labels instead of over the fields themselves.

I'm open to other ideas for how to present this info!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tell you what. I'm going to merge this in with the knowledge that we might need to iterate over how to best display this on the page -- but that we'll display it on the page somehow rather than in a new page, so it's a matter of adjusting the JS display code. This unblocks me from putting up a second PR that relies on this code being in.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For what it's worth, I tested on all mobile devices I had available to me, and was able to get tooltips for everything (which doesn't mean that all have the ability, just that all I tested did, and I didn't even try browserstack). The main issue I see is being able to tell which fields have tooltips and which don't across the site. You might find that people expect tooltips on everything that looks alike, elsewhere in the site.

@cpeel cpeel merged commit 3f4f284 into DistributedProofreaders:master Dec 26, 2025
9 checks passed
@cpeel cpeel deleted the better-pophelp branch December 26, 2025 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants