@Alsee:
> A full list of breaking wikitext would be great help for that.
The Flow team pushed that line for the last six years. It is both impossible, and futile.
It is a basic, fundamental step in software development. Not futile, nor impossible. If you want to help, collecting test cases is one way to do so. Not necessary to collect all, but the more you collect, the better the coverage and the resulting software.
should be able to copy and save a basic text string without corruption.
The copy-paste issue was the most frustrating I've met in Flow (although you might be talking about another copy issue...). I was pleasantly surprised that it was fixed soon after my report.
However, you've responded to the current prototype (that has nothing to do with Flow) with "I am begging you, please let me help you." and now criticize Flow's old bugs that might not be fixed already, instead of helping by collecting test cases.
That approach failed for the last six years. That approach will fail for next six years.
Now we are talking about Flow and the new talk pages - two fundamentally different products - at the same time, confusingly mixing assertions about either this or that in the same sentence... It makes no sense and it is kind of unhelpful.
I should not that we are conducting this discussion in the current Flow version, without issues. While the Flow "approach failed" to replace talk pages, it is a usable product, even if not as fast and convenient as reddit, which has threaded discussions and visual editor (wysiwyg) that can be switched to source editor (markdown), so basically the same feature set.
that we have to start from scratch with a better design.
The prototype started from scratch and Parsoid was recently rewritten in PHP.
I'm trying to help the Foundation get the design right this time.
Sorry to say this: the way you try to do that is confused, focusing on dramatic words instead of accurate terminology and exact use-cases.
It is very very simple: I'm not editing with VE, I don't want to edit with VE, don't run the text back and forth through VisualEditor's software stack.
To help first clarify to yourself what is the subject at hand: it's not Flow and not VE anymore. I think you are confusing Parsoid - a small part of all VE's modules - with VE.
For example when someone edits one part of the page and the software corrupts the content on an unrelated part of the page.
I'm saying that it is not some random bug. Bugs aren't supposed to be predictable. When I tested the prototype I was able to predict and immediately confirm that it was broken in this manner.
The examples you tested would be very helpful if you were to copy those into your answer.