New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WordPress.com Toolbar: Most links unclickable on touch devices. #7529

Closed
bisko opened this Issue Jul 25, 2017 · 4 comments

Comments

3 participants
@bisko
Contributor

bisko commented Jul 25, 2017

How to reproduce:

  1. Have a Jetpack site with WordPress.com toolbar enabled
  2. Open a page
  3. Open the toolbar
  4. Try to click on Blog posts/Pages and Add

What's happening:

Nothing :(

What should be happening:

The link should be followed and the specified section opened.

Notes:

  • Happens on Touch enabled devices (or touch events emulation enabled in Chrome)
  • Sometimes it does nothing, sometimes it opens the notifications panel
  • Reproducible on iOS, Android and Chrome on macOS with touch emulation enabled
  • Seems to be happening only on Jetpack enabled sites, WordPress.com sites are not affected.

out

( There is no cursor, but you can notice the items tapped get highlighted )

cc @michaeldcain @lancewillett @designsimply @marekhrabe @folletto

@designsimply

This comment has been minimized.

designsimply commented Jul 25, 2017

Possibly related: #6993 cc @vindl

@jeherve

This comment has been minimized.

Member

jeherve commented Mar 20, 2018

Could you give this another try with the current Bleeding edge version of the Jetpack plugin, thanks to the Beta plugin?

I wonder if the issue may have been fixed by the different fixes we've made to the masterbar recently.

Thank you!

@stale

This comment has been minimized.

stale bot commented Sep 16, 2018

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@stale stale bot added the [Status] Stale label Sep 16, 2018

@jeherve

This comment has been minimized.

Member

jeherve commented Sep 17, 2018

Closing this for now because of the lack of activity on this. We can always reopen in the future if needed.

@jeherve jeherve closed this Sep 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment