https://bugzilla.wikimedia.org/show_bug.cgi?id=49686
--- Comment #17 from Oliver Keyes <[email protected]> --- So, let's calm down here. We're not "pissing on" anyone; we're choosing to prioritise. Right now the devs have got a lot of open bugs for the VisualEditor - things that actively /don't work/. They've got a lot of features still to build, and a lot of expectations about the project. Personally, I'm incredibly impressed with the speed of change and the patches that have been submitted so far - it's a fantastic workrate. But that doesn't change the fact that there's still a lot to do. Now: we /can/ have wikitext converted to VE-compatible elements. But there are a few costs. First: from my conversations with the developers, I understand that doing it on the fly would slow the VE down very substantially. You'd have to automatically parse and re-render the page. Second: if they work on this, there's a lot of stuff that is going to get pushed back. We have a VisualEditor. It's great, it's miles better than anything else produced to do this job in MediaWiki, but it still needs a lot of work and still has a lot of active bugs - problems parsing content, problems rendering content. If enhancements such as this (which would certainly be nice) are worked on, active breakage will take a back seat: those areas where it simply doesn't have features will take a back seat. I'm not comfortable with saying that we rate "being able to type markup into the VisualEditor" higher than "being able to manipulate tables". As you note, the source editor is still available in all namespaces. Users who are actively prioritising familiarity with syntax, and their muscle memory, are welcome to use it. It's not going away. In the meantime, the VE development process should be focused on making it work full stop, not making it work for the users who are highly comfortable with source editing. That's nice, and it's something I'd love to see, but it's not going to happen if actual bugs aren't fixed first. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
