Help talk:VisualEditor

Disabling the VisualEditor
The VisualEditor formats template code contrary to legibility and established convention and often encourages very poor formatting (leaving colored HTML (span style="font:Arial:; line-height:1em; color:yellow" and all that shit), etc.), is there a way to disble it? I am aware that Wikia wants anons to edit easier and wants people to "have a better experience editing without seeing code" but it creates a many headaches for people who believe in true wiki editing (coding). The template coding inconsistency is especially a problem; I don't want to see every darned parameter on one monolithic line. Alamko7 (talk) 03:22, July 29, 2015 (UTC)


 * Can send in specific examples of the bad formatting to Special:Contact/bug? We'll want to look into this in more depth there. Besides that, we recognise the single-line approach for templates is not ideal - it's something that's on our list to change in the future. 14:52, July 29, 2015 (UTC)
 * I would say that the HTML is not entirely the fault of VisualEditor (perhaps bad formatting is the wrong word... overzealous prservation of formatting?) but rather the fault belongs to unaware users who think it is fine to copy and paste from Word and VisualEditor's WYSIWIG abilities (it is such a pain to clean up those rampant "mso-font-family-ja-ar-en-etc: Arial Meiryo Tahoma" rubbish! WYSIWIG has its upsides and downsides... Occasionally an anon even somehow manages to copy-and-paste a template instead of using it the right way resuting in an expanded template HTML code in an article...) Meanwhile, the template formatting is a problem that would be most easily solved by providing the option to disable VisualEditor. I understand that fixing this is in the pipeline but VisualEditor is the sole source of these headaches and disabling it in the meantime would do wonders for readibility and ease of editing. Alamko7 (talk) 04:49, July 30, 2015 (UTC)
 * We have strong evidence that the VE has pretty positive effects on editing overall, so it's not something we'd like to do without strong evidence of problems. This is something we can investigate in more depth via Special:Contact, however :) 14:56, July 30, 2015 (UTC)

Bug
I hope someone's watching this page, I'm not seeing a bug report form specifically for VisualEditor.

Anyway, in case this isn't already known, VisualEditor messes up parsing when there are tags of the "include" family placed inside templates holding table components.

On my wiki specifically, the code looked like: // This is the table header // Table closer - just "|}", actually

This ends up rendering both a template and a "literal" table. The table is exactly what the template should look like, and you can edit by double-clicking on the cells, but it's entirely separate from the actual template and won't interact with it. Meanwhile, the actual template is invisible (just a single spacebar of whitespace), placed above the table that came from nowhere, and it's really easy to miss if you don't look carefully.

(I'll upload a screenshot if anyone wants it, I didn't want to upload right away in case there was some kind of rule against that.)

It looks like the glitch still happens when the  is changed to   or. My quick tests with the header/closer and the content inside the tags weren't very conclusive of effects, so I'm not sure if they do contribute to the bug as well.

-Illumini9 (talk) 10:53, September 30, 2015 (UTC)


 * All bugs should be reported via Special:Contact/bug - could you send this it to there (with links to test examples, if possible), please? Thanks! 11:48, September 30, 2015 (UTC)