It apears to have been resolved by now.
The issue still appears on SO

The issue regressed here on MSE as well

I recently got access to the 10K-tools, and the inline tag editor, which I observed to crop the suggested tags by the boundaries of the tag box on my mobile, using the responsive design.

While writing this question on a desktop, I noticed the same problem on the ask a question page. See attached screenshot, where there should be a suggested design tag, but it is hidden.

When I use the inline tag editor on the question using FF on a desktop, it works as expected.

Regular editor: enter image description here

10K inline tag editor:

enter image description here

Using FF 68.5.0esr on Mac and using Chrome 85.0.4183.81 on Android.

  • Cross-site duplicate on MSO: Tags tooltip not working. Commented Sep 2, 2020 at 12:57
  • 2
    Got nothing to do with inline editor or mobile device: it's empty everywhere and anywhere. JS code bug, that is also not browser specific. Commented Sep 2, 2020 at 15:19
  • Same here. An annoying regression.
    – Drew
    Commented Sep 2, 2020 at 16:10
  • @Drew the prod deploy is happening right now Commented Sep 2, 2020 at 16:14
  • 1
    @ShadowWizardWearingMask pedantic maybe, but the JS is innocent here; the problem was at the server Commented Sep 2, 2020 at 16:19
  • @Marc well, the server did send a result back so couldn't know the result isn't proper. :) Commented Sep 2, 2020 at 17:26
  • @Marc by the way, any chance the fix broke notifications? Didn't get notification for your comment... :-( (oh ooops wrong circle, but you still see the comment directed at me below) Commented Sep 2, 2020 at 17:29
  • @user400654 not now.. this one worked. Commented Sep 2, 2020 at 17:39
  • @Shadow well I got the notification, so... Commented Sep 2, 2020 at 19:15
  • @Marc me too, now. Just random glitch then? Notification going poof? Commented Sep 2, 2020 at 19:21

2 Answers 2


This is my fault, a side-effect of some infrastucture changes. Sorry. Working on getting a fix out ASAP.

For those who are interested in code things: some newly "async" code was not properly "awaited", and the result (now a future/promise, not a value) was handed to a JSON serializer, which duly serialized... the future/promise :(

For those who are not interested in code things: it is now fixed.


It's not being "cropped". There are literally no child elements in the .tag-suggestions div.

enter image description here

Even though the data is being returned.

enter image description here

  • 3
    Adapted the title based on your research.
    – Luuklag
    Commented Sep 2, 2020 at 14:41
  • 5
    The second image here should be sufficient for anyone suitably experienced in .NET to be able to chuckle in a way that says "heh, I know what Marc did there..." Commented Sep 2, 2020 at 16:15

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .