# The popup menu for quoting text is unresponsive on Android
**URL:** https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332
**Category:** Bug
**Tags:** reactions
**Created:** [11 juli 2026 om 16:51 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332 "2026-07-11T16:51:39Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [11 juli 2026 om 16:51 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/1 "2026-07-11T16:51:39Z")
I cannot highlight and quote text on Android atm. This has been the case for some time. What am I missing? (Android 16 & 17, Chrome)
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [11 juli 2026 om 17:19 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/2 "2026-07-11T17:19:08Z")
I have this happen once in awhile. Unable to highlight text. Thought at present is working
> [@merefield](#):
>
> What am I missing? (Android 16 & 17, Chrome)
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [12 juli 2026 om 02:24 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/3 "2026-07-12T02:24:13Z")
I’m assuming the following don’t help?
1. Reload
2. Try reacting to a post until you see the reactions popup, then try highlighting text
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [12 juli 2026 om 08:31 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/4 "2026-07-12T08:31:16Z")
> [@NateDhaliwal](#):
>
> 1. Try reacting to a post until you see the reactions popup, then try highlighting text
Wow. That fixes it! What the … that’s the strangest workaround I’ve ever come across! Thanks!
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [12 juli 2026 om 08:36 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/5 "2026-07-12T08:36:25Z")
Yep, it’s happened to me before, and this has always managed to fix it.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [12 juli 2026 om 08:39 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/6 "2026-07-12T08:39:48Z")
I wonder if this relates to some stale localStorage? Very interesting.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [12 juli 2026 om 08:41 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/7 "2026-07-12T08:41:14Z")
Hm. I’ve always thought it to be something to do with states. Like forcing the reactions popup would force the hover state to be active again. But that’s just speculation.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [12 juli 2026 om 09:24 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/8 "2026-07-12T09:24:15Z")
Just happened again.
And the workaround worked again.
Going to class this as #Contribute > Bug
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [12 juli 2026 om 10:31 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/9 "2026-07-12T10:31:19Z")
## AI (GPT 5.6 Sol Ultra) diagnosis in Codex (if useful):
Found it: Discourse Reactions leaks a global “no text selection” state.
- Reaction touchstart adds discourse-reactions-no-select to in `plugins/discourse-reactions/assets/javascripts/discourse/components/discourse-reactions-actions.gjs:222`.
- That class applies user-select: none and disables WebKit’s long-touch callout for the entire document in `plugins/discourse-reactions/assets/stylesheets/common/discourse-reactions.scss:1`.
- If a vertical scroll starts over the reaction button, `plugins/discourse-reactions/assets/javascripts/discourse/components/discourse-reactions-actions.gjs:249` invalidates the gesture without removing the class.
- `plugins/discourse-reactions/assets/javascripts/discourse/components/discourse-reactions-actions.gjs:257` then returns early, leaving the class behind indefinitely.
- There is also no touchcancel or component-destruction cleanup.
The only removal is in `plugins/discourse-reactions/assets/javascripts/discourse/components/discourse-reactions-actions.gjs:690`. That explains the reported workaround ([The popup menu for quoting text is unresponsive on Android](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332)): opening and dismissing the reactions popup calls collapseAllPanels(), restoring selection.
The quote toolbar itself is downstream—it listens for selectionchange and requires a real browser selection in `frontend/discourse/app/components/post-text-selection.gjs:58`. With global user-select: none, Android never creates that selection.
History confirms this bug family: a 2023 scrolling fix ([FIX: prevents triggering a reaction while scrolling (#224) · discourse/discourse-reactions@d1970cf · GitHub](https://github.com/discourse/discourse-reactions/commit/d1970cf750e82a3035e05ddc3d52733a5c76a6ab)) introduced the invalid-touch early return, and a 2024 partial fix ([FIX: couldn't select text after dismissing a reaction (#296) · discourse/discourse-reactions@c6710ef · GitHub](https://github.com/discourse/discourse-reactions/commit/c6710ef909481fd2fc16c10405f3daa92b6481fc)) moved cleanup to panel collapse but left scroll/cancel paths uncovered.
So in summary it’s the combination:
1. `touchStart` adds the global `discourse-reactions-no-select` class.
2. `touchMove` marks the scrolling gesture invalid but does not clear it.
3. `touchEnd` sees the invalid gesture and returns early.
4. No popup opened, so `collapseAllPanels()` never clears the class.
That leaves the entire page with `user-select: none`. `touchcancel` is another uncovered path, but the `vertical-scroll` path is the primary crux.
The fix should clear the class on every completed, rejected, cancelled, or destroyed touch lifecycle, with regression tests for `touchstart → touchmove → touchend` and `touchcancel`.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [12 juli 2026 om 12:07 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/10 "2026-07-12T12:07:00Z")
This bug has bothered me for some time now, glad you’ve found a fix 👍
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [14 juli 2026 om 07:29 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/11 "2026-07-14T07:29:37Z")
@davidb for your attention
---
### Author:  [@tannerabread](https://meta.discourse.org/u/tannerabread)
#### Post date: [14 juli 2026 om 21:18 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/12 "2026-07-14T21:18:57Z")
> [@merefield](#):
>
> This has been the case for some time
Hi @merefield I’m trying to see if this is related to the other fix I had put out a couple of weeks ago. It should have been isolated to iOS so I’m curious, how long is “some time”? Is that a couple of weeks or longer?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [14 juli 2026 om 21:45 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/13 "2026-07-14T21:45:23Z")
Gosh, apologies I cannot recall accurately but my hunch is at least a couple of weeks, though I’m not entirely sure.
I’m fairly certain this was a problem under Android 16 so that is before the Pixel rollout.
In any case of course this might not be isolated to Android …
---
### Author:  [@tannerabread](https://meta.discourse.org/u/tannerabread)
#### Post date: [14 juli 2026 om 21:46 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/14 "2026-07-14T21:46:46Z")
No worries, I’ll do some testing locally without the changes and see if it was my iOS fix that caused this. If it was, the patch I put out today might help, but I’ll verify first.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [14 juli 2026 om 21:47 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/15 "2026-07-14T21:47:15Z")
Thanks for looking at it!
---
### Author:  [@akatsukinoluna](https://meta.discourse.org/u/akatsukinoluna)
#### Post date: [15 juli 2026 om 10:33 UTC](https://meta.discourse.org/t/the-popup-menu-for-quoting-text-is-unresponsive-on-android/407332/16 "2026-07-15T10:33:52Z")
> [@tannerabread](#):
>
> > [@merefield](#):
> >
> > This has been the case for some time
>
> Hi @merefield I’m trying to see if this is related to the other fix I had put out a couple of weeks ago. It should have been isolated to iOS so I’m curious, how long is “some time”? Is that a couple of weeks or longer?
I have been experiencing this issue on Android Chrome for multiple months on one website I think. (Though I too was not keeping exact track, until a second site I use updated two days ago)