Why is this LSEP symbol showing up on Chrome and not Firefox or Edge?

Unicode Character Encoding Ascii Non Ascii-Characters

Unicode Problem Overview

So this web page is rendering with these symbols and they are found throughout this website/application but on no other sites. Can anyone tell me

What this symbol is?
Why it is showing up only in one browser?

Unicode Solutions

Solution 1 - Unicode

That character is U+2028 Line Separator, which is a kind of newline character. Think of it as the Unicode equivalent of HTML’s  .

As to why it shows up here: my guess would be that an internal database uses LSEP to not conflict with literal newlines or HTML tags (which might break the database or cause security errors), and either:

The server-side scripts that convert the database to HTML neglected to replace LSEP with  
Chrome just breaks standards by displaying LSEP as a printing (visible) character, or
You have a font installed that displays LSEP as a printing character that only Chrome detects. To figure out which font it is, right click on the offending text and click “Inspect”, then switch to the “Computed” tab on the right-hand panel. At the very bottom you should see a section labeled “Rendered Fonts” which will help you locate the offending font.

More information on the line separator, excerpted from the Unicode standard, Chapter 5.8, Newline Guidelines (on p. 12 of this PDF):

> # Line Separator and Paragraph Separator > > A paragraph separator—independent of how it is encoded—is used to indicate a > separation between paragraphs. A line separator indicates where a line break > alone should occur, typically within a paragraph. For example: > > > This is a paragraph with a line separator at this point,
> > causing the word “causing” to appear on a different line, but not causing
> > the typical paragraph indentation, sentence breaking, line spacing, or
> > change in flush (right, center, or left paragraphs). > > For comparison, line separators basically correspond to HTML  , and > paragraph separators to older usage of HTML  (modern HTML delimits > paragraphs by enclosing them in ...). In word processors, paragraph > separators are usually entered using a keyboard RETURN or ENTER; line > separators are usually entered using a modified RETURN or ENTER, such as > SHIFT-ENTER. > > A record separator is used to separate records. For example, when exchanging > tabular data, a common format is to tab-separate the cells and to use a CRLF > at the end of a line of cells. This function is not precisely the same as line > separation, but the same characters are often used. > > Traditionally, NLF started out as a line separator (and sometimes record > separator). It is still used as a line separator in simple text editors such as > program editors. As platforms and programs started to handle word processing > with automatic line-wrap, these characters were reinterpreted to stand for > paragraph separators. For example, even such simple programs as the Windows > Notepad program and the Mac SimpleText program interpret their platform’s NLF > as a paragraph separator, not a line separator. Once NLF was reinterpreted to > stand for a paragraph separator, in some cases another control character was > pressed into service as a line separator. For example, vertical tabulation VT > is used in Microsoft Word. However, the choice of character for line separator > is even less standardized than the choice of character for NLF. Many Internet > protocols and a lot of existing text treat NLF as a line separator, so an > implementer cannot simply treat NLF as a paragraph separator in all > circumstances.

Solution 2 - Unicode

I found that in WordPress the easiest way to remove "L SEP" and "P SEP" characters is to execute this two SQL queries:

UPDATE wp_posts SET post_content = REPLACE(post_content, UNHEX('e280a9'), '')
UPDATE wp_posts SET post_content = REPLACE(post_content, UNHEX('e280a8'), '')

The javascript way (mentioned in some of the answers) can break some things (in my case some modal windows stopped working).

Solution 3 - Unicode

You can use this tool... http://www.nousphere.net/cleanspecial.php

...to remove all the special characters that Chrome displays.

Steps: Paste your HTML and Clean using HTML option.

You can manually delete the characters in the editor on this page and see the result.

Paste back your HTML in file and save :)

Solution 4 - Unicode

I recently ran into this issue, tried a number of fixes but ultimately I had to paste the text into VIM and there was an extra space I had to delete. I tried a number of HTML cleaners but none of them worked, VIM was the key!

Solution 5 - Unicode

9999years answers is great.

In case you use Symfony with Twig template I would recommend to check for an empty Twig block. In my case it was an empty Twig block with an invisible char inside.

The LSEP char was only displayed on certain device / browser. On the other I had a blank space above the header and I could not see any invisible char.

I had to inspect the GET request to see that the value 1f18 was before the open html tag.

Once I removed an empty Twig block it was gone.

hope this can help someone one day ...

Solution 6 - Unicode

My problem was similar, it was "PSEP" or "P SEP". Similar issue, an invisible character in my file.

I replaced \x{2029} with a normal space. Fixed. This problem only appeared on Windows Chrome. Not on my Mac.

Solution 7 - Unicode

I agree with @Kapil Bathija - Basically you can copy & paste your HTML code into http://www.nousphere.net/cleanspecial.php and convert it.

Then it will convert the special characters for you - Just remove the spaces in between the words and you will realize you have to press backspace 2x meaning there is an invalid character that can't be translated.

I had the same issue and it worked just fine afterwards.

Solution 8 - Unicode

You can also copy the text, paste it into a HTML editor such as Coda, remove the linebreak, copy it and paste it back into your site.

Video here: https://www.loom.com/share/501498afa7594d95a18382f1188f33ce

Solution 9 - Unicode

Looks like my client pasted HTML into Wordpress after initially creating it with MS-Word. Even deleting the
and visible spaces did not fix the issue. The extended characters became visible in vi/vim.

If you don't have vi/vim available, try highlighting from 2 chars before the LSEP to 2 chars after the LSEP; delete that chunk, and re-type the correct characters.

Content Type	Original Author	Original Content on Stackoverflow
Question	Joseph	View Question on Stackoverflow
Solution 1 - Unicode	9999years	View Answer on Stackoverflow
Solution 2 - Unicode	LeoGal	View Answer on Stackoverflow
Solution 3 - Unicode	Kapil Bathija	View Answer on Stackoverflow
Solution 4 - Unicode	Peter	View Answer on Stackoverflow
Solution 5 - Unicode	Kaizoku Gambare	View Answer on Stackoverflow
Solution 6 - Unicode	Michael Douma	View Answer on Stackoverflow
Solution 7 - Unicode	jP_	View Answer on Stackoverflow
Solution 8 - Unicode	Andy	View Answer on Stackoverflow
Solution 9 - Unicode	Danny	View Answer on Stackoverflow