On Tue, Jul 23, 2013 at 2:14 PM, John Vandenberg <jayvdb(a)gmail.com> wrote:
There is an enhancement for that.
https://bugzilla.wikimedia.org/show_bug.cgi?id=51897
IMO the current behaviour isnt correct. There are so few instances
that nowiki is desirable, that the current VE should refuse to accept
wikitext (at least [[ and {{, and maybe ==, # and * at beginning of
line, etc ), until at least such time as they have sorted out all the
other bugs causing this to happen unintentionally. If the user needs
to input [[ or {{ they can use the source editor. Or the VE could
walk the user through each nowiki and either a) ask the user to
confirm they want the obvious fix done automatically for them, or b)
help them fix the problem. Before saving.
We disagree on that one then. VisualEditor is meant to hide wikitext
entirely. The primary focus is on people that don't know wikitext. I
agree that we should keep nowiki-fication to a minimum and get rid of
the other bugs that cause this to happen, but I think the action we
currently take when a user types in wikitext (which is to warn them
and say "this won't work") is appropriate. VE is meant to be a visual
editor, not a
visual-except-with-weird-shortcuts-that-only-make-sense-if-you-know-the-legacy-markup-we-used-before-your-time
editor.
That's my opinion. Actual product direction is not something I'm in
charge of, that's James F's job, but AFAIK our current product
direction is similar to what I just said.
That's because the lines start with a space, which triggers a <pre> if
not nowiki-ed. Obviously the correct thing to do there is just remove
the space, but we haven't fixed that yet.
Once again that's people typing wikitext into VE, which is not supported.
A lot of those are parts of symptoms of other bugs, and I'm pretty
sure a few of them are duplicates. <nowiki> often appears when
something else goes wrong and Parsoid attempts to fix things.
Roan