Oneboxing comments in chat is broken when there is a forward slash before the number sign. http://stackoverflow.com/questions/19894363/expecting-a-declaration-c/#comment29596719_19894363, for example, doesn’t trigger oneboxing while http://stackoverflow.com/questions/19894363/expecting-a-declaration-c#comment29596719_19894363 does.

  • When is this an issue exactly? Whenever you copy a comment link, it doesn't have /#, just #. Where are you getting the /# syntax from so regularly that you need it oneboxed in chat? – jmac Nov 11 '13 at 5:53
  • 1
    @jame The problem is that sometimes it does have /#. – rightfold Nov 11 '13 at 7:29
  • Could you give an example? If I go to the question in question, and hover over the comment time to get the link to it, it displays as http://stackoverflow.com/questions/19894363/expecting-a-declaration-c#comment29596719_19894363, the only time I get /# is if I follow your first link which already includes the /# so it appears that something is odd in a changing hyperlink depending on how you got to the page. For normal browsing though, I can't recreate it. – jmac Nov 11 '13 at 7:31
  • 2
    The bug is whatever added a slash to the URL. It should not be there in the first place, as jmac also mentioned. – Shadow The Burning Wizard Nov 11 '13 at 8:58
  • @jmac It occurs when there is a new comment and you load it through AJAX. – rightfold Nov 22 '13 at 22:29

You must log in to answer this question.

Browse other questions tagged .