Everyone deserves a happy ending.In theaters July 26. #DeadpoolWolverine► Watch Marvel on Disney+: https://bit.ly/2XyBSIW► Subscribe to Marvel on YouTube: ht...
The & error occurs when somebody types “&” but it shows up as & in messages or titles due to some sort of problem with parsing or sanitizing the text input, idk the specifics. In order to even show this on lemmy.today I had to type that amp; part in manually a second time because it automatically changed to “&” otherwise. It’s been around for more than a decade already.
It is not an error. It is an html code (for ampersand, all codes start with &, in this case amp means ampersand) that for some technical reason that is beyond me gets wrongly parsed into text.
Well, it’s not just a Lemmy issue at all, though. It’s on a bunch of websites across all the browsers I’ve ever used. It’s kind of neat if it weren’t so dumb that it’s persisted for so long.
Feels weird to me that the & error still exists. Who do we have to blame for this, Google?
What do you mean?
The & error occurs when somebody types “&” but it shows up as & in messages or titles due to some sort of problem with parsing or sanitizing the text input, idk the specifics. In order to even show this on lemmy.today I had to type that amp; part in manually a second time because it automatically changed to “&” otherwise. It’s been around for more than a decade already.
Lol. I don’t think what you’re describing is an issue for all clients. I’m using Sync and all I’m seeing is ampersands displayed correctly.
Ah, for reference then:
Does this in Liftoff as well. Always takes me a moment to remember what’s happening in the titles.
It is not an error. It is an html code (for ampersand, all codes start with &, in this case amp means ampersand) that for some technical reason that is beyond me gets wrongly parsed into text.
So it’s not an error it’s just that the applications are coded such that sometimes it incorrectly displays it in a way that it shouldn’t, got it.
It’s a Lemmy v.18 issue, so instances like Lemmy.world that haven’t updated yet still see it happen.
Well, it’s not just a Lemmy issue at all, though. It’s on a bunch of websites across all the browsers I’ve ever used. It’s kind of neat if it weren’t so dumb that it’s persisted for so long.
The what error?
The amp; error that follows after ampersands.
I don’t see it in Sync it seems.