The new tag popup makes it easy to watch or ignore particular tags and shows the tag info excerpt. Here's one on EL&U:

Single-word-requests tag excerpt

However, the full tag info contains a lot more information which helps users. Getting at that information is not obvious: you need to click the View tag link which provides a list of questions and an abbreviated excerpt, and then click the Learn more... link.

The old tag pop-up used to include a link to the full tag info, and it appears that this was implemented as a result of a request in 2011 which changed behaviour which was remarkably similar to what happens now.

Here's an example I found to give the idea. The Info link showed the full tag info.

enter image description here

The current behaviour is a regression, breaking something which was previously fixed.

Could View tag in the new popup be changed to Other questions and a new More info link be included which gives easier access to the full tag info? Perhaps something like this...

Proposed alternative

  • Agree, but as far as I can see, in the new UX there's simply no proper place for "info" link. Not expert though, so hopefully UX expert can find such a place. Aug 14, 2018 at 11:51
  • 3
    If anything that link should not be titled info but read more ... and I agree that it should be reintroduced on the tag popup
    – rene
    Aug 14, 2018 at 11:59
  • Related, if not a duplicate: Restore previous variant of tag popup – but I think this very post is more clear so maybe we need to close the other way around.
    – rene
    Aug 14, 2018 at 12:01
  • @rene I thought one moderator or another must have asked about this already, but I couldn't find it. As a mod myself, linking to the page in a comment is still a possibility, but I would really like users to find it for themselves. Aug 14, 2018 at 12:05
  • There's a userscript that adds this functionality: stackapps.com/questions/8054/improved-tag-popup
    – Barmar
    Apr 21, 2020 at 15:21
  • Unfortunately userscripts don't help those who don't know about them, in particular first-time users who actually need the extended tag info. Apr 21, 2020 at 15:23
  • 2
    It's a little disappointing that despite the "bug" tag, and being obviously a regression error, no-one from SE has reacted in nearly a year. Apr 21, 2020 at 15:24
  • 1
    I'm not sure its an error, but its certainly something worth relooking May 16, 2020 at 14:04
  • 2
    Heads up that this is on our list to revisit. Going to look into this with our UX team and see what we can do to address.
    – Jon Chan
    Aug 5, 2020 at 19:05
  • 1
    @JonChan why not status-review then? Aug 5, 2020 at 19:08
  • 2
    @ShadowWizardWearingMask We've been using status-review for items that get raised to us, but once we actually finish triaging them, we want to indicate it's in the plan for us to address, just not in the short term (also why it's not status-planned and status-deferred instead). We're still experimenting with some of this.
    – Jon Chan
    Aug 5, 2020 at 19:13
  • 2
    @JonChan While it's buoying that the issue has at long last been recognised, it is a regression error, a bug, objectively harmful to the user experience (especially for new users), and easy to fix. It's even more disappointing that it won't be fixed quickly and is being deliberately pushed even further on to the back burner. Aug 5, 2020 at 19:17
  • 1
    I'm afraid I agree with Andrew, bitter experience proves that bugs/requests in status deferred just never get fixed. Maybe one or two ever. :/ Aug 5, 2020 at 19:40
  • @JonChan This has now been "status-deferred" for 18 months. Any news? Feb 3, 2022 at 13:32
  • @JonChan And now more than six months after that... Dec 9, 2022 at 12:54


You must log in to answer this question.

Browse other questions tagged .