We are having a very similar problem to that was described here:
Here’s what I found after some testing on the forum with a resized viewport to simulate mobile and DevTools: the reactions popup is definitely there. The element shows up and goes away as expected when hovering and removing the cursor. But for some reason, it does not appear on-screen. Or at least it seems to.
Well, here’s a screenshot when hovering:
[image]
If you look really closely at the area just above the bottom red line above the thumbs-up button, you can see a faint shadow, which is …
The reactions picker is displayed outside of the view port.
Using debug tools I was able to determine that is receives element.style {left: 89.6562px; top: 2375.19px; }. Since this is an element style I haven’t had any success in fiddling with some other css to affect this.
If I resize my screen to be something like 3000px tall, I can actually see the picker there.
We do not have the jira plugin determined to be the culprit here: Unable to use reactions on IOS/Mobile - #23 by Don
We are using the custom reactions theme component: Custom Discourse Reactions - #14 by Don I don’t see how that could have this effect though.
Unfortunately I cannot provide a full list of plugins we do have right now, as I have no administrator privileges.
3 לייקים
chapoi
4 בפברואר, 2026, 3:26pm
2
I would be useful to try in safe mode though, just to make sure.
לייק 1
I did not realize, I could simply try safe mode without any privileges.
After that was pointed out to me, I observed that
a) Reactions are a plugin, so disabling all plugins got rid of the problem in an unhelpful way ^^
b) More importantly: With no themes, everything works fine.
The only theme that should have any interaction with reactions is
Contribute to VaperinaDEV/discourse-custom-reactions development by creating an account on GitHub.
The reactions definitely worked correctly a few weeks ago and that theme has not changed in years.
Either it interacts weirdly with a recent discourse update or something broke in our configuration. I will try to inquire more.
לייק 1
I have done some additional digging:
My guess is, that this commit in the discourse core is what caused the break:
committed 12:23AM - 09 Dec 25 UTC
Specifically this:
computePosition(referenceElement, floatingElement, {
placement: "top",
middleware: [
offset(-5),
shift({ limiter: limitShift() }),
flip({ padding: 5 }),
],
}).then(({ x, y }) => {
Object.assign(floatingElement.style, {
left: `${x}px`,
top: `${y}px`,
});
});
seems to interact badly with this styling from the theme component:
Deactivating this css line in the dev tool doesn’t change the position of the currently displayed reactions picker, but causes the next one to be placed correctly.
לייק 1
chapoi
5 בפברואר, 2026, 2:12pm
5
Your best bet would be to reach out to the author of that theme component and ask them to fix it. Maybe they are not aware of it yet.
2 לייקים
I have just opened an issue there.
2 לייקים
The theme component has been updated and the issue resolved.
2 לייקים
