In T253389#6158799, @cscott wrote:

Any double spaces in the output include at least one  , not literal 0x20 ASCII space characters. It may be that you were able to search for them before by cut-and-pasting an existing "double-space" (including the not-visibly-different non-breaking-space).

In T253389#6158762, @cscott wrote:

It's a design feature of HTML that spaces are collapsed. This allow folks like me (see over there <-) to use double spaces after a period when typing, and *almost all* markup languages will collapse or reformat them for presentation. This is how TeX works, how LaTeX works, how markdown works (which is what I'm using in this comment), how wikitext works, and how HTML works.

Feature, not bug.

In T253389#6158760, @Reedy wrote:

I did. You reverted it. Check the task history.

In T253389#6158701, @Reedy wrote:

I'm also really not sure what bug you're reporting. As far as I can see, the source text has numerous double spaces, presumably because the author/editors have added them. I've removed a load from Memory Leak in https://en.wikipedia.org/w/index.php?title=Memory_leak&type=revision&diff=958231010&oldid=956138383 . If I then edit the article again, they don't reappear

I'm not sure why you'd expect the MW parser (or anything else) to fix/remove double spaces in text unless it was explicitly made to do so. Which AFAIK it's not, and probably shouldn't either. If people have added them, they probably want them to be there, or have added them erroneously.

In T253389#6158720, @Reedy wrote:

Wikimedia software

I'm also not sure what "Wikimedia software" is. The software is MediaWiki. Wikimedia is the name for the group of websites.

In T253389#6158701, @Reedy wrote:

not Firefox, because it can't search effectively for multiple spaces

Doesn't seem to be the case

Pinging @matmarex and @JTannerWMF.

Pinging @matmarex and @JTannerWMF.

Pinging @matmarex and @JTannerWMF.

Pinging @matmarex and @JTannerWMF.

Pinging @matmarex and @JTannerWMF.

Pinging @matmarex and @JTannerWMF.

Pinging @matmarex and @JTannerWMF.

@Whatamidoing-WMF The issue I have is with formatting, as mentioned on the linked issue, not sections.

Reopened at T247241.

Is this supposed to have been fixed? Because it isn't.

It's not a Chrome bug. The behaviour I describe in the original post is a VisualEditor bug.

That issue I just linked seems to be unrelated but very similar. Either way, I filed a bug report for it too since it was pissing me off: https://bugs.chromium.org/p/chromium/issues/detail?id=1054854

@matmarex Thank you for all this additional info. I had in fact drafted up a Chromium bug report before commenting on this until I tested it on an Chromium version older than the issue and confirmed what I thought, that it was triggered by a VisualEditor update rather than a Chrome one.

@matmarex @JTannerWMF Someone needs to hear about this. It's driving me insane.

In T151671#5871380, @Schnark wrote:

In T151671#5871286, @SUM1 wrote:

This means I can't find all spaces that come after new lines, which are the problem in this article. Even if there weren't spaces, I couldn't find all pipes after new lines (like you would see in an infobox, but here they're not appropriate). I also can't replace them.

You can use ^\s+ to find all spaces after a linebreak. That probably won't help you much, as merging lines by replacing is not possible, but at least finding something at the start (or end) of a line indeed is possible.

This is incredibly frustrating as I've been trying to remove a bunch of terribly formatted citations on Wikipedia (meaning they can't be edited in VisualEditor, where searching for "\n" or "\u000a" would work in matching the line feed character ↵ if it were in text):

This issue has never been fixed. Adding some additional confirmatory details to the issue. @Aklapper

In T239550#5704331, @Schnark wrote:

This works for me without any issues, both with the HotCat gadget enabled (as seen on the screenshots) and without it.

In T239550#5704782, @Aklapper wrote:

@SUM1: Which exact Wikipedia website is this about?

Should also mention that this totally breaks the editor, at least it did for me.

Just thought I'd point out it's not the same issue as https://phabricator.wikimedia.org/T220174. The issue is very different to the video provided there, it occurs on desktop, does not occur in reading mode and it did not occur that early. But who knows, they may be linked.

In T227415#5311693, @Aklapper wrote:

Edit a Wikipedia article then click the "Cite" button

Which Wikipedia? Any link to an example article? Which editor is used?

I can't reproduce the edit at all in my sandbox, and I believe my first report was a false alarm caused by confusing markup diff appearance.

@ssastry I don't recall switching at all when I made my Prion edit.

@ssastry I'm back at a standstill, can't reproduce the bug again. I'll keep testing.

@ssastry The reporting user didn't experience the bug herself (to my knowledge) but encountered numerous other people's edits being affected.

In T219023#5055241, @Arlolra wrote:

Since about a week ago, ...

@SUM1 Are you suggesting this used to work? @ssastry claims this bug was present in Parsoid since at least the beginning of the year,
https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/498513#message-dbb28282cd4e9bf37bfe1e126e2efe5f89d72ef6

This bug affects Wikipedia, Wikimedia, Wiktionary and probably other WMF websites (but the MediaWiki website itself seems to be case sensitive with links, so this bug is not possible).

They vandalised practically all of the tasks I started. :(