# Core 讨论区 +1 反应悬停弹出窗口的 Bug
**URL:** https://meta.discourse.org/t/core-discourse-reactions-bug-with-1-reaction-hover-popover/403520
**Category:** Bug
**Tags:** reactions
**Created:** [2026年五月21日 11:11 UTC](https://meta.discourse.org/t/core-discourse-reactions-bug-with-1-reaction-hover-popover/403520 "2026-05-21T11:11:27Z")
**Posts on this page:** 1
**Showing post:** 2
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2026年五月21日 11:12 UTC](https://meta.discourse.org/t/core-discourse-reactions-bug-with-1-reaction-hover-popover/403520/2 "2026-05-21T11:12:41Z")
感谢你的报告 @PortChange 👍 这将在以下链接中修复
>
>
> The \`findReactionUsers\` model method built its query string via plain template-l…iteral concatenation, e.g. \`?reaction\_value=${value}\`. For reactions whose value contains URL-reserved characters — most notably the default \`+1\` (thumbs-up) — this produced \`?reaction\_value=+1\`, which Rack decodes as \`reaction\_value=" 1"\`. The controller then queried for that mangled value, returned an empty \`reaction\_users\` array, and the hover tooltip on the small emoji in the post reactions counter rendered its loading spinner indefinitely (the \`{{#each ... else}}\` branch fires when the users collection stays undefined).
>
> Switch to passing the value through ajax's \`data:\` option so jQuery serializes it via \`$.param\` (which uses \`encodeURIComponent\`). This matches what the sibling \`fetchReactionsUsersList\` (new menu) already does and means the request reaches the backend as \`%2B1\`.
>
> While here, update the \`PostReactionsList\` page object to use \`\[id="..."\]\` instead of the bare \`#id\` CSS selector, so it tolerates reaction values that contain characters disallowed in unescaped ID selectors. This unlocks a regression spec that hovers over a \`+1\` reaction and verifies the user list populates.
>
> Ref - t/184216
---
_[View the full topic](https://meta.discourse.org/t/core-discourse-reactions-bug-with-1-reaction-hover-popover/403520)._