popojargo
commented
4 years ago This is an Ace editor issue. This should be properly rendered and it's working on other editors. I'm looking forward fixing it.
Open DarrenCook opened 5 years ago
popojargo
commented
4 years ago This is an Ace editor issue. This should be properly rendered and it's working on other editors. I'm looking forward fixing it.
Expected Behavior
The \u00A0 character should just appear as a space. (it is the unicode equivalent of
)Current Behavior
It shows as a white dot in a red square, in the Fauxton interface, when I click a document to view/edit it.
Possible Solution
A workaround:
I'm using node.js and the nano library, and if I use
s.replace(/\u00A0/g, ' ')before doingdb.insert(s, 'mydoc')then the problem goes away. But I'd rather not have to modify the data in this way. (A user might have used non-breaking space deliberately.)Context
It is only distracting. The \u00A0 appears to be stored correctly.
Your Environment
Fauxton on Apache CouchDB v. 2.3.1
(On Linux, viewing with Firefox 68)