6

Yesterday, I have received a notification about a post (namely the Opt-in alpha test for a new Stacks editor), that I followed, so I can see (and vote for) the new bugs/features reported/requested.

Screenshot

I thought is for some summary of bugs, or an issue tracker used by this project, or something like that.

However, I found this:

Answer to Opt-in alpha test for a new Stacks editor

Ah, OK, and . However, the tag-formatted texts slipped together.


The issue is probably on the backend, as the buggy HTML element contains only plaintext, and it has no space in it.

4
  • 1
    Hey, thats my post :). Have an upvote for the excellent example. – Luuklag Apr 21 at 7:52
  • @Luuklag You already have my vote on your bug report ;) – FZs Apr 21 at 7:57
  • Most likely duplicate of Search doesn't space out tags in a post. The representation of tags as plaintext (used in search and in notifications, most likely using the same method) is just the text content of the tags. If there’s no space between them in the post, then there won’t be a space in the plaintext representation. Not sure what you mean by “as the buggy HTML element contains only plaintext” — there is no buggy HTML element and whether or not it contains only plaintext doesn’t seem relevant. – Sebastian Simon Apr 22 at 0:34
  • @SebastianSimon Yes, it seems likely that the two issues were caused by the same problem, but I wouldn't say anything until a staff member looks at it. By "as the buggy HTML element contains only plaintext", I meant that the issue isn't a CSS styling bug, but a plaintext representation problem coming from the server. Yes, there's no buggy HTML element, I meant the HTML element that contains the bug. – FZs Apr 22 at 6:00

You must log in to answer this question.

Browse other questions tagged .