enter image description here

Here is the problem. For some reason Arqade comments don't onebox (I tried with http and https)

I tried to onebox the comment https://gaming.stackexchange.com/questions/257112/how-do-i-change-my-name-on-steam/#comment357863_257114 (The chat message is here)

  • 1
    That one doesn't work but others are just fine... not all of Arqade's comments fail to onebox.
    – Catija
    Nov 12, 2016 at 21:28
  • @Catija Huh, that's weird Nov 12, 2016 at 21:29
  • 2
    That question seems to be the issue. Comments on other questions work fine... that one doesn't. Not sure why.
    – Catija
    Nov 12, 2016 at 21:33

2 Answers 2


Regex, it's always the regex. Seriously now, the reason is a rogue trailing slash you have in the URL, which is not supposed to be there.

If you browse to the ordinary question URL which is https://gaming.stackexchange.com/questions/257112/how-do-i-change-my-name-on-steam the comment links will onebox just fine, e.g. https://gaming.stackexchange.com/questions/257112/how-do-i-change-my-name-on-steam#comment357863_257114.

However, if somehow you end up adding a slash after the title in the url, which is https://gaming.stackexchange.com/questions/257112/how-do-i-change-my-name-on-steam/, everything still appears fine however the comment links become what you described and indeed won't onebox.

The bug is whatever gave you that URL, if it was internal SE link and not added manually by someone.

Onebox can of course remove it as well, but not sure if it's worth the efforts.

  • 1
    When I was testing, I got the link in the normal way - right click - copy link. So, directly from the date stamp. Not sure why this question has the issue. Other comments on that question do the same thing.
    – Catija
    Nov 12, 2016 at 22:59
  • @Catija because you copied the link provided by the OP here (or clicked the link in chat), which already got the slash. Ordinary link, e.g. the question title on arqade, is fine and doesn't have the slash. Nov 12, 2016 at 23:00
  • 1
    Ah. I see. Hmmm.
    – Catija
    Nov 12, 2016 at 23:01
  • @Catija yeah... also looked in search results, link there is fine. Dunno where that slash came from, maybe some fancy userscript someone got, always adding slashes... or maybe someone was just messing around. Nov 12, 2016 at 23:02

I don't think you should naturally end up with trailing slashes like that at any point, but I know I've ended up with them after instinctively cleaning 286893#286893 from a the end of URL like http://meta.stackexchange.com/questions/286892/comments-dont-onebox/286893#286893.

For people like us, oneboxing of comment URLs with such trailing slashes is now supported.

You must log in to answer this question.

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