Ah, thank you for the feedback! I'll explain it better in the post.
The reason why Google "breaks" is because   is decimal HTML entity whereas is the same character in "human" version of the html, which Google doesn't speak. Hope this clarified it!
I noticed an interesting behaviour, when I wrote   in the dev.to markdown(without the enclosings), and did the preview, nothing was visible in the comment screen area. But in text editor I was able to type it.
Do try this.
Same goes for Google, if you add a space in Google search bar and try searching for it, Google won't search, but if you will enter   this will be visible but when submitted, it will be converted into a blank space. And google can't search for blank space, because there is nothing on the search bar after submitting it.
Ah, thank you for the feedback! I'll explain it better in the post.
The reason why Google "breaks" is because
 is decimal HTML entity whereas is the same character in "human" version of the html, which Google doesn't speak. Hope this clarified it!I too want to add something,
I noticed an interesting behaviour, when I wrote
 in the dev.to markdown(without the enclosings), and did the preview, nothing was visible in the comment screen area. But in text editor I was able to type it.Do try this.
Same goes for Google, if you add a space in Google search bar and try searching for it, Google won't search, but if you will enter
 this will be visible but when submitted, it will be converted into a blank space. And google can't search for blank space, because there is nothing on the search bar after submitting it.Lol, it's all hilarious. I just noticed that you can't even start a google search with a space 🤓
Correct we can't Google a blank space 😂.