# 태그 정보 버튼이 어디로 갔나요?

**URL:** https://meta.discourse.org/t/where-did-the-tag-info-button-go/402436
**Category:** UX
**Created:** [5월 7, 2026, 9:15오후 UTC](https://meta.discourse.org/t/where-did-the-tag-info-button-go/402436 "2026-05-07T21:15:57Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [6월 8, 2026, 8:25오후 UTC](https://meta.discourse.org/t/where-did-the-tag-info-button-go/402436/10 "2026-06-08T20:25:38Z")

</div>

좋은 발견이에요! 그 플러그인은 컴포넌트를 재사용하지만 동일한 데이터를 사용할 수 없어요… 이렇게 하면 버튼이 숨겨집니다:

> <https://github.com/discourse/discourse/pull/40657>
>
> Reported here: https://meta.discourse.org/t/where-did-the-tag-info-button-go/402…436/9
> 
> When the \`Navigation\` component gets reused in a different context, like in the \[ActivityPub plugin\](https://github.com/discourse/discourse-activity-pub) we need to check for \`toggleTagInfo\` which lives in the \`discovery/list.js\` controller — otherwise it's assumed that \`toggleTagInfo\` is present and the tag-info button appears and does not function. 
> 
> So in core nothing will change, but in customizations that reuse the \`Navigation\` component, authors will have to decide to explicitly show the button.

---

_[View the full topic](https://meta.discourse.org/t/where-did-the-tag-info-button-go/402436)._