User:Fram/Sandbox

2013-12-05 (MW 1.23wmf6)

VisualEditor was updated as part of the wider [1.23wmf6 branch deployment] on Thursday 5 December. In the two weeks since 1.23wmf5, the team worked on some new features, performance and usability improvements, minor bug fixes and code infrastructure.

You can now paste rich content copied from external sources (not just as plain text), including other VisualEditor surfaces (bugs 41193, 48170, 50128, and 53828). You can paste the clipboard as plain (unformatted) text by using a new keyboard shortcut, Ctrl+⇧ Shift+V or ⌘ Cmd+⇧ Shift+V (bug 53781). It is now possible to edit auto-numbered external links (i.e. one that appears like "[3]"); you can change the target using the link inspector as with other links. If you change it to an internal link, it will replace the auto-numbered anchor with the name of the target (bug 53505). You can now launch into VisualEditor by appending ?veaction=edit to the view page URL irrespective of user preferences – this will let users test VisualEditor with a variety of browsers without needing to log in each time (bug 55900).

We now optimistically submit the page Parsoid for serialisation into wikitext as soon as the user launches the save dialog, before they've clicked "save page", which should make saving the page appear faster for many use cases (bug 56011). If you have loaded the wikitext diff of a page ("Review your changes")

and then try to save it without making changes, VisualEditor will keep a
copy of the wikitext from the first time, so saving will be much faster
(bug 55979). 

We significantly changed how VisualEditor stores the contents of the page internally (from UTF-8 back to UTF-16), which fixes a large number of issues related to inserting, deleting, cursoring around and selecting over non-Latin scripts like Devanagari, Arabic or Thai (bugs 51472, 51596, 51846, 53757). We now annotate the body tag of the HTML document with a class ("ve-activated") so gadget authors can ensure they don't fire in VisualEditor mode (bug 57555).

A bug which meant that switching to wikitext when logged out always gave an edit conflict warning has been fixed (bug 56835). Auto-numbered external links now also auto-number when they appear in generated content like reference lists (bug 57420).

Cursoring over a generated content node (a media file, template, 

reference or similar) now does not get you stuck in an infinite cursoring loop in Firefox (bug 57600).

Clicking in the blank space above the link inspector now closes the 

inspector, so you won't get a pawn ("♙") appearing if you try to insert content there (bug 56976). A bug that effected the rendering of <source> blocks in the MWExtensionNode, causing it to appear empty after the user edits it is now fixed (bug 54577).

A regression that meant that the "watch this" checkbox in the save 

dialog was checked regardless of the user preference was reversed (bug 56206).

The browser tests now test the media insertion dialog, and were updated a number of times to keep up with changes to VisualEditor. [[1]] is now available in MediaWiki core for other users, and [UI] was extended, with additional widgets including checkboxes and generic labels. The automated testing system has been greatly expanded to cover script and input-method-editor issues, with an IME simulator able to check every change in the code for breaking any of dozens of known IME tools; further information about new IMEs can be added as it is gathered, and a tool to help collect this information is now available.

You can monitor the automated browser tests' results (triggered every twelve hours) live on the server. A complete list of individual code commits is available [the 1.23/wmf6 changelog], and all Bugzilla bugs closed in this period are on Bugzilla's list.