For MMORPG: Martial Gamer, A reader gave us feedback that the everything in the <>, that we use for system notifications and game details, cannot be seen at all. This problem appears when the novel is read in Mozilla Firefox, and when Internet Explorer is used, the <> brackets and everything within them are displayed correctly.
Display issue with <> in novel
TeamSparrow Can you give us the url of the chapter that has display issue ?
TeamSparrow We have checked some chapters of this book, but there is no display issue. Maybe it is the issue of the browser. Do you know the browser version the reader is using ?
renjialelele Mozilla Firefox and Internet Explorer.
Neverfire7 I think he was asking for the precise version number.
ryuxenji Ah, I see. I wouldn't know the versions... 
Neverfire7
you can find the browser version in "About firefox" or "About Google Chrome"
Tested out Firefox:
Chapter 143 was used.
The version was 59.0.2 and up to date.
There seemed to be no problem, however.
I also tested this issue on the Webnovel App (2.6.0), Firefox App (59.0.2), Chrome App (65.0.3325.109) and the Chrome Browser (65.0.3325.181), however, no issues cropped up either. I could read the chapter, including the bits between <>.
[unknown]
Yes, we can't reproduce this issue, perhaps we can [unknown] to tell us his browser version, thanks.
- Edited
OP is probably using the video ad skip userscript. The guy who coded it used a lazy method to look for <p> tags. He just assumed anything in the chapter content surrounded by <> was a <p> tag and stripped it.
The end result is that anything surrounded by <> won't be displayed.
EDIT:
Just took a look at the code. Apparently, the text surrounded by <> isn't stripped. It's assumed to be an HTML tag instead and isn't displayed for that reason.
Jeebus666 Wow, Thanks for your amazing discovery. Third party extension is not recommended, though.
I had it happen in ryuxenji's novel whilst i was reading eith Qidian App.
maybe different problem tho, translator said it somehoe deleted any name he put in <>, so not a didplay problem.
so maybe, not that i think about it, not thatuseful opps.