User talk:Stratocaster27

(contribs · [ deletions] · [ moves] · deleted edits · cross-wiki · wikichecker · count · pages created · [ logs])

GA reviewing
Okay, a page is waiting for you at WikiProject Good articles/Recruitment Centre/Recruiter Central/Archives/Stratocaster27 whenever you're ready. Thanks again for your interest. -- Khazar2 (talk) 21:21, 4 July 2013 (UTC)

VE newsletter
Hey Stratocaster27; hope you had a decent weekend :). We've got a pile of patches, some of which went out on Monday, some yesterday:


 * If you insert wikitext such as links or section headers, you get a notice in the top right corner (over the save button). It doesn't go away until click, though once dismissed you don't get another one that edit. (49820)
 * If your edit token expires, VE fetches a new one for you so you can save. (50424)
 * If the page is empty of content but does have something non-content (like a category or an HTML comment), VE no longer crashes on load - (50289)
 * sub tags are no longer removed ((49873)
 * If you type at the end of links, they now extend
 * Templates now only take a single click to insert
 * Clear annotations clears links (50461)
 * The link inspector stays open when you click to another item (50895)
 * Typing after multi-byte characters no longer creats pawn icons (51140)
 * Resizing thumbnails that have a default size set now works (50645)
 * References made by tag:ref now display properly (50978)
 * The VE is integrated with the spam blacklist (50826)
 * Feedbacl link goes to the right language (47730)

There are a lot more improvements coming, but that's it for Monday and Tuesday. Thanks, Okeyes (WMF) (talk) 08:32, 17 July 2013 (UTC)

VE newsletter
Hey Stratocaster27. The newest updates: Along with some miscellaneous language support fixes. That's all for today; as always, let us know if you spot more bugs. Thanks, Okeyes (WMF) (talk) 22:07, 24 July 2013 (UTC)
 * Links now don't extend over space/punctuation/workbreaks when you type (51463)
 * Users with the "minoredit" preference set get working functionality (51515)
 * You can tab to buttons in dialogs, including the save dialog (50047)
 * We now show the (or ) message as an edit notice (51459)
 * You can scroll dialog panels like in transclusions' templates' parameter listings (51739)
 * Templates that only create meta-data and no display content at all (like Template:Use dmy dates) now can't be deleted accidentally or deliberately, but still don't show up (51322)
 * FlaggedRevisions integration (49699)
 * Edit summary will get the section title pre-added if you launched from a section edit link (50872)

GA reviewing
Hey Strato, hadn't heard from you in a bit and thought I'd follow up--are you still interested in GA reviewing? -- Khazar2 (talk) 00:53, 2 August 2013 (UTC)

VisualEditor newsletter for 06 August 2013
It's been almost two weeks since the last newsletter, and a lot of improvements have been made during that time. The main things that people have noticed are significant improvements to speed for typing into long pages, scrolling and deleting  on large pages. There have also been improvements to references, with the latest being support for list-defined references, which are s defined inside a ) (bug 53345).  Selecting both an image and some text, and then trying to add a link, previously deleted the selected image and the text.  This was fixed in bug 50127. There was another problem related to using arrow keys to move the cursor next to an inline image that was fixed (bug 53507).

Looking ahead: The next planned upgrade is scheduled for next Thursday, and you should expect to find a redesigned toolbar with drop-down menus that include room for references, templates, underline, strikethrough, superscript, subscript, and code formatting. There will also be keyboard shortcuts for setting the format (paragraph vs section headings).

If you are active at other Wikipedias, the next group of Wikipedias to have VisualEditor offered to all users is being determined at this time. Generally speaking, languages that depend on the input method editor are not going to receive VisualEditor this month. The current target date is Tuesday, September 24 for logged-in users only. You can help with translating the documentation. In several cases, most of the translation is already done, and it only needs to be copied over to the relevant Wikipedia. If you are interested in finding out whether a particular Wikipedia is currently on the list, you can leave a message for me at my talk page.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) (talk) 21:44, 5 September 2013 (UTC)

VisualEditor newsletter for September 19, 2013
VisualEditor has been updated twice in the last two weeks. As usual, what is now running on the English Wikipedia had a test run at Mediawiki during the previous week.

As announced, the toolbar was redesigned to be simpler, shorter, and to have the ability to have drop-down groups with descriptions. What you see now is the initial configuration and is expected to change in response to feedback from the English Wikipedia and other Wikipedias. The controls to add  (underline),   (subscript), and   (superscript),   (strikethrough) and   (computer code/monospace font) annotations to text are available to all users in the drop-down menu. At the moment, all but the most basic tools have been moved into a single drop-down menu, including the tools for inserting media, references, reference lists, and templates. The current location of all of the items in the toolbar is temporary, and your opinions about the best order are needed! Please offer suggestions at VisualEditor/Feedback/Toolbar.

In an eagerly anticipated upgrade to the reference dialog, newly added references or reference groups no longer need the page to be saved before they can be re-used (bugs 51689 and 52000). The 'Use existing reference' button is now disabled on pages which don't yet have any references (bug 51848). The template parameter filter in the transclusion dialog now searches both parameter name and label (bug 51670).

In response to several requests, there are some new keyboard shortcuts. You can now set the block/paragraph formatting from the keyboard: Ctrl sets a block as a regular paragraph; Ctrl up to Ctrl sets it as a Heading 1 ("Page title") to Heading 6 ("Sub-heading 4"); Ctrl sets it as pre-formatted (bug 33512). Ctrl, which creates level 2 section headings, may be the most useful.

Some improvements were made to capitalization for links, so typing in "iPhone" will offer a link to "iPhone" as well as "IPhone" (bug 50452).

Copying and pasting within the same document should work better as of today's update, as should copying from VisualEditor into a third-party application (bug 53364, bug 52271, bug 52460). Work on copying and pasting between VisualEditor instances (for example, between two articles) and retaining formatting when copying from an external source into VisualEditor is progressing.

Major improvements to editing with input method editors (IMEs; mostly used for Indic and East Asian languages) are being deployed today. This is a complex change, so it may produce unexpected errors. On a related point, the names of languages listed in the "languages" (langlinks) panel in the Page settings dialog now display as RTL when appropriate (bug 53503).

Looking ahead: The help/'beta' menu will soon expose the build number next to the "Leave feedback" link, so users can give more specific reports about issues they encounter (bug 53050). This change will make it easier for developers to identify any cacheing issues, once it starts reporting the build number (currently, it says "Version false"). Also, inserting a link, reference or media file will put the cursor after the new content again (bug 53560). Next week’s update will likely improve how dropdowns and other selection menus behave when they do not fit on the screen, with things scrolling so the selected item is always in view.

If you are active at other Wikipedias, the next group of Wikipedias to have VisualEditor offered to all users is being finalized. About two dozen Wikipedias are on the list for Tuesday, September 24 for logged-in users only, and on Monday, September 30 for unregistered editors. You can help with translating the documentation. In several cases, most of the translation is already done, and it only needs to be copied over to the relevant Wikipedia. If you are interested in finding out whether a particular Wikipedia is currently on the list, you can leave a message for me at my talk page.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) (talk) 21:46, 19 September 2013 (UTC)

VisualEditor newsletter on 16 October 2013
VisualEditor is still being updated every Thursday. As usual, what is now running on the English Wikipedia had a test run at Mediawiki during the previous week. If you haven't done so already, you can turn on VisualEditor by going to your preferences and choosing the item, " ".

The reference dialog for all Wikipedias, especially the way it handles citation templates, is being redesigned. Please offer suggestions and opinions at mw:VisualEditor/Design/Reference Dialog. (Use your Wikipedia username/password to login there.) You can also drag and drop references (select the reference, then hover over the selected item until your cursor turns into the drag-and-drop tool). This also works for some templates, images, and other page elements (but not yet for text or floated items). References are now editable when they appear inside a media item's caption (bug 50459).

There were a number of miscellaneous fixes made: Firstly, there was a bug that meant that it was impossible to move the cursor using the keyboard away from a selected node (like a reference or template) once it had been selected (bug 54443). Several improvements have been made to scrollable windows, panels, and menus when they don't fit on the screen or when the selected item moves off-screen. Editing in the "slug" at the start of a page no longer shows up a chess pawn character ("♙") in some circumstances (bug 54791). Another bug meant that links with a final punctuation character in them broke extending them in some circumstances (bug 54332). The "page settings" dialog once again allows you to remove categories (bug 54727). There have been some problems with deployment scripts, including one that resulted in VisualEditor being broken for an hour or two at all Wikipedias (bug 54935). Finally, snowmen characters ("☃") no longer appear near newly added references, templates and other nodes (bug 54712).

Looking ahead: Development work right now is on rich copy-and-paste abilities, quicker addition of citation templates in references, setting media items' options (such as being able to put images on the left), switching into wikitext mode, and simplifying the toolbar. A significant amount of work is being done on other languages during this month. If you speak a language other than English, you can help with translating the documentation.

For other questions or suggestions, or if you encounter problems, please let everyone know by posting problem reports at VisualEditor/Feedback and other ideas at Wikipedia talk:VisualEditor. Thank you! Whatamidoing (WMF) (talk) 18:47, 16 October 2013 (UTC)

VisualEditor newsletter for November 2013
Since the last newsletter, the VisualEditor team has worked on some feature changes, major infrastructure improvements to make the system more stable, dependable and extensible, some minor toolbar improvements, and fixing bugs.

A new form parsing library for language characters in Parsoid caused the corruption of pages containing diacritics for about an hour two weeks ago. Relatively few pages at the English Wikipedia were affected, but this created immediate problems at some other Wikipedias, sometimes affecting several dozen pages. The development teams for Parsoid and VisualEditor apologize for the serious disruption and thank the people who reported this emergency at VisualEditor/Feedback and on the public IRC channel, #mediawiki-visualeditor.

There have been dozens of changes since the last newsletter. Here are some of the highlights:


 * Accidental deletion of infoboxes and other items: You now need to press the Delete or Backspace key twice to delete a template, reference or image. The first time, the item becomes selected, and the second time, it is removed.  The need to press the delete key twice should make it more obvious what you are doing and help avoid accidental removals of infoboxes and similar (bug 55336).
 * Switch from VisualEditor to the wikitext editor: A new feature lets you make a direct, one-way editing interface change, which will preserve your changes without needing to save the page and re-open it in the wikitext editor (bug 50687). It is available in a new menu in the action buttons by the Cancel button (where the "Page Settings" button used to be). Note that this new feature is not currently working in Firefox.
 * Categories and Languages are also now directly available in that menu. The category suggestions drop-down was appearing in the wrong place rather than below its input box, which is now fixed. An incompatibility between VisualEditor and the deployed Parsoid service that prevented editing categories and language links was fixed.
 * File:, Help: and Category: namespaces: VisualEditor was enabled for these namespaces the on all wikis (bug 55968), the Portal: and Viquiprojecte: namespaces on the Catalan Wikipedia (bug 56000), and the Portal: and Book: namespaces on the English Wikipedia (bug 56001).
 * Media item resizing: We improved how files are viewed in a few ways. First, inline media items can now be resized in the same way that has been possible with block ones (like thumbnails) before. When resizing a media item, you can see a live preview of how it will look as you drag it (bug 54298). While you are dragging an image to resize it, we now show a label with the current dimensions (bug 54297). Once you have resized it, we fetch a new, higher resolution image for the media item if necessary (bug 55697). Manual setting of media item sizes in their dialog is nearly complete and should be available next week. If you hold down the shift key whilst resizing an image, it will now snap to a 10 pixel grid instead of the normal free-hand sizing. The media item resize label now is centered while resizing regardless of which tool you use to resize it.
 * Undo and redo: A number of improvements were made to the transactions system which make undoing and redoing more reliable during real-time collaboration (bug 53224).
 * Save dialogue: The save page was re-written to use the same code as all other dialogs (bug 48566), and in the process fixed a number of issues. The save dialog is re-accessible if it loses focus (bug 50722), or if you review a null edit (bug 53313); its checkboxes for minor edit, watch the page, and flagged revisions options now layout much more cleanly (bug 52175), and the tab order of the buttons is now closer to what users will expect (bug 51918). There was a bug in the save dialog that caused it to crash if there was an error in loading the page from Parsoid, which is now fixed.
 * Links to other articles or pages sometimes sent people to invalid pages. VisualEditor now keeps track of the context in which you loaded the page, which lets us fix up links in document to point to the correct place regardless of what entry point you launched the editor from—so the content of pages loaded through   and   both now have text links that work if triggered (bug 48915).
 * Toolbar links: A bug that caused the toolbar's menus to get shorter or even blank when scrolled down the page in Firefox is now fixed (bug 55343).
 * Numbered external links: VisualEditor now supports Parsoid's changed representation of numbered external links (bug 53505).
 * Removed empty templates: We also fixed an issue that meant that completely empty templates became impossible to interact with inside VisualEditor, as they didn't show up (bug 55810).
 * Mathematics formulae: If you would like to try the experimental LaTeX mathematics tool in VisualEditor, you will need to opt-in to Beta Features. This is currently available on Meta-wiki, Wikimedia Commons, and Mediawiki.org. It will be available on all other Wikimedia sites on 21 November.
 * Browser testing support: If you are interested in technical details, the browser tests were expanded to cover some basic cursor operations, which uncovered an issue in our testing framework that doesn't work with cursoring in Firefox; the Chrome tests continue to fail due to a bug with the welcome message for that part of the testing framework.
 * Load time: VisualEditor now uses content language when fetching TemplateData information, so reducing bandwidth use, and users on multi-language or multi-script wikis now get TemplateData hinting for templates as they would expect (bug 50888).
 * Reuse of VisualEditor: Work on spinning out the user experience (UX) framework from VisualEditor into oojs-ui, which lets other teams at Wikimedia (like Flow) and gadget authors re-use VisualEditor UX components, is now complete and is being moved to a shared code repository.
 * Support for private wikis: If you maintain a private wiki at home or at work, VisualEditor now supports editing of private wikis, by forwarding the Cookie: HTTP header to Parsoid ( set to true) (bug 44483).  (Most private wikis will also need to install Parsoid and node.js, as VisualEditor requires them.)

Looking ahead: If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 22:12, 20 November 2013 (UTC)
 * VisualEditor will be released to some of the smaller Wikipedias on 02 December 2013. If you are active at one or more smaller Wikipedias where VisualEditor is not yet generally available, please see the list at VisualEditor/Rollouts.
 * Public office hours on IRC to discuss VisualEditor with Product Manager James Forrester will be held on Monday, 2 December, at 1900 UTC and on Tuesday, 3 December, at 0100 UTC. Bring your questions.  Logs will be posted on Meta after each office hour completes.
 * In terms of feature improvements, one of the major infrastructure projects affects how inserting characters works, both using your computer's built-in Unicode input systems and through a planned character inserter tool for VisualEditor. The forthcoming rich copying and pasting feature was extended and greater testing is currently being done.  Work continues to support the improved reference dialog to quickly add citations based on local templates.

VisualEditor newsletter • 19 December 2013
Since the last newsletter, the VisualEditor team has worked on some toolbar improvements, fixing bugs, and improving support for Indic languages as well as other languages with complex characters. The current focus is on improving the reference dialog and expanding the new character inserter tool.

There have been dozens of changes since the last newsletter. Here are some of the highlights:

Looking ahead: The transclusion dialog will see further changes in the coming weeks, with a simple mode for single templates and an advanced mode for more complex transclusions. The new character formatting menu on the toolbar will get an arrow to show that it is a drop-down menu. The reference dialog will be improved, and the Reference item will become a button in the main toolbar, rather than an item in the Insert menu.
 * Rich copying and pasting is now available. If you copy text from another website, then character formatting and some other HTML attributes are preserved.  This means, for example, that if you copy a pre-formatted suggested citation from a source like this, then VisualEditor will preserve the formatting of the title in the citation.  Keep in mind that copying the formatting may include formatting that you don't want (like section headings).  If you want to paste plain, unformatted text onto a page, then use Control or Command  (Mac).
 * Auto-numbered external links like can now be edited just like any other link.  However, they cannot be created in VisualEditor easily.
 * Several changes to the toolbar and dialogs have been made, and more are on the way. The toolbar has been simplified with a new drop-down text styles menu and an "insert" menu. Your feedback on the toolbar is wanted here.  The transclusion/template dialog has been simplified.  If you have enabled mathematical formula editing, then the menu item is now called the formula editor instead of LaTeX.
 * There is a new character inserter, which you can find in the new "insert" menu, with a capital Omega ("Ω"). It's a very basic set of characters.  Your feedback on the character inserter is wanted here.
 * Saving the page should seem faster by several seconds now.
 * It is now possible to access VisualEditor by manually editing the URL, even if you are not logged in or have not opted in to VisualEditor normally. To do so, append   to the end of the page name.  For example, change   to   to open a random page in VisualEditor.  This is intended to support bug testing across multiple browsers, without requiring editors to login repeatedly.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at VisualEditor/Feedback. Thank you! Whatamidoing (WMF) (talk) 20:41, 19 December 2013 (UTC)

VisualEditor newsletter for Janaury 2014
Since the last newsletter, the VisualEditor team has worked mostly minor features and fixing bugs. A few significant bugs include working around a bug in CSSJanus that was wrongly flipping images used in some templates in right-to-left (RTL) environments (bug 50910) a major bug that meant inserting any template or other transclusion failed (bug 59002), a major but quickly resolved problem due to an unannounced change in MediaWiki core, which caused VisualEditor to crash on trying to save (bug 59867). This last bugs did not appear on any Wikipedia. Additionally, significant work has been done in the background to make VisualEditor work as an independent editing system.

As of today, VisualEditor is now available as an opt-out feature to all users at 149 active Wikipedias.


 * The character inserter tool in the "Insert" menu has a very basic set of characters. The character inserter is especially important for languages that use Latin and Cyrillic alphabets with unusual characters or frequent diacritics. Your feedback on the character inserter is requested. In addition to feedback from any interested editor, the developers would particularly like to hear from anyone who speaks any of the 50+ languages listed under Phase 5 at mw:VisualEditor/Rollouts, including Breton, Mongolian, Icelandic, Welsh, Afrikaans, Macedonian, and Azerbaijani.
 * meta:Office hours on IRC have been heavily attended recently. The next one will be held this coming Wednesday, 22 January at 23:00 UTC.
 * You can now edit some of the page settings in the "options" dialog –    and   as selection (forced on, forced off, or default setting; bugs 56866 and 56867) and   as a checkbox (bug 57166).
 * The automated browser tests were adjusted to speed them up and bind more correctly to list items in lists, and updated to a newer version of their ruby dependencies. You can monitor the automated browser tests' results (triggered every twelve hours) live on the server.
 * VisualEditor/User guide was updated recently to show some new and upcoming features.

Looking ahead: The character formatting menu on the toolbar will get a drop-down indicator next Thursday. The reference and media items will be the first two listed in the Insert menu. The help menu will get a page listing the keyboard shortcuts. Looking further out, image handling will be improved, including support for alignment (left, right, and center) and better control over image size (including default and upright sizes). The developers are also working on support for editing redirects and image galleries.

Subscriptions to this newsletter are managed at VisualEditor/Newsletter. Please add or remove your name to change your subscription settings. If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 20:06, 17 January 2014 (UTC)

VisualEditor Newsletter—February 2014
Since the last newsletter, the VisualEditor team has worked on some small changes to the user interface, such as moving the reference item to the top of the Insert menu, as well as some minor features and fixing bugs, especially for rich copying and pasting of references.

The biggest change was the addition of more features to the image dialog, including the ability to set alignment (left, right, center), framing options (thumbnail, frame, frameless, and none), adding alt text, and defining the size manually. There is still some work to be done here, including a quick way to set the default size.


 * The main priority is redesigning the reference dialog, with the goal of providing autofill features for ISBNs and URLs and streamlining the process. Current concept drawings are available at VisualEditor/Design/Reference Dialog. Please share your ideas about making referencing quick and easy with the designers.
 * A few bugs in the existing reference dialog were fixed. The toolbar was simplified to remove galleries and lists from the reference dialog.  When you re-use references, it now correctly displays the references again, rather than just the number and name.  If you paste content into a dialog that can't fit there (e.g.   in references), it now strips out the inappropriate HTML.
 * You can now edit image galleries inside VisualEditor. At this time, the gallery tool is a very limited option that gives you access to the wikitext.  It will see significant improvements at a later date.
 * The character inserter tool in the "Insert" menu is being redesigned. Your feedback on the special character inserter is still wanted, especially if you depend on Wikipedia's character inserters for your normal editing rather than using the ones built into your computer.
 * You can now see a help page about keyboard shortcuts in the page menu (three bars next to the Cancel button).
 * If you edit categories, your changes will now display correctly after saving the page.
 * Saving the page should be faster now.
 * Any community can ask to test a new tool to edit TemplateData by leaving a note at.

Looking ahead: The link tool will tell you when you're linking to a disambiguation or redirect page. The warning about wikitext will hide itself after you remove the wikitext markup in that paragraph. Support for creating and editing redirects is in the pipeline. Looking further out, image handling will be improved, including default and upright sizes. The developers are also working on support for viewing and editing hidden HTML comments, some behavioral magic words like DISPLAYTITLE, and in-line language setting.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 04:21, 20 February 2014 (UTC)

VisualEditor newsletter—March 2014
Since the last newsletter, the VisualEditor team has mostly worked on changes to the template and image dialogs.

The biggest change in the last few weeks was the redesign of the template dialog. The template dialog now opens in a simplified mode that lists parameters and their descriptions. (The complex multi-item transclusion mode can be reached by clicking on "Show options" from inside the simplified template dialog.) Template parameters now have a bigger, auto-sizing input box for easier editing. With today's update, searching for template parameters will become case-insensitive, and required template parameters will display an asterisk (*) next to their edit boxes. In addition to making it quicker and easier to see everything when you edit typical templates, this work was necessary to prepare for the forthcoming simplified citation dialog. The main priority in the coming weeks is building this new citation dialog, with the ultimate goal of providing autofill features for ISBNs, URLs, DOIs and other quick-fills. This will add a new button on the toolbar, with the citation templates available picked by each wiki's community. Concept drawings can be seen at VisualEditor/Design/Reference Dialog. Please share your ideas about making referencing quick and easy with the designers.


 * The link tool now tells you when you're linking to a disambiguation or redirect page. Pages that exist, but are not indexed by the search engine, are treated like non-existent pages.
 * Wikitext warnings will now hide when you remove wikitext from the paragraph you are editing.
 * The character inserter tool in the "Insert" menu has been slightly redesigned, to introduce larger buttons. Your suggestions for more significant changes to the special character inserter are still wanted.
 * The page options menu (three bars, next to the Cancel button) has expanded. You can create and edit redirect pages, set page options like ,   and   , and more.  New keyboard shortcuts are listed there, and include undoing the last action, clearing formatting, and showing the shortcut help window.  If you switch from VisualEditor to wikitext editing, your edit will now be tagged.
 * It is easier to edit images. There are more options and they are explained better.  If you add new images to pages, they will also be default size.  You can now set image sizes to the default, if another size was previously specified. Full support for upright sizing systems, which more readily adapt image sizes to the reader's screen size, is planned.
 * VisualEditor adds fake blank lines so you can put your cursor there. These "slugs" are now smaller than normal blank lines, and are animated to be different from actual blank lines.
 * You can use the Ctrl or Command shortcuts to open the save window, and you can preview your edit summary when checking your changes in the save window.
 * After community requests, VisualEditor has been deployed to the Interlingual Occidental Wikipedia, the Portuguese Wikibooks, and the French Wikiversity.
 * Any community can ask for custom icons for their language in the character formatting menu (bold, italic, etc.) by making a request on Bugzilla or by contacting Product Manager James Forrester.

The developers apologize for a regression bug with the deployment on 6 March 2014, which caused the incorrect removal of  size definitions on a handful of pages on the English Wikipedia, among others. The root cause was fixed, and the broken pages were fixed soon after.

Looking ahead: Several template dialogs will become more compact. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. You will be able to see the Table of Contents change live as you edit the page, rather than it being hidden. In-line language setting may be offered to a few Wikipedias soon.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at VisualEditor/Feedback or by joining the office hours on 19 April 2014 at 2000 UTC. Thank you! MediaWiki message delivery (talk) 22:44, 20 March 2014 (UTC)

VisualEditor newsletter—April 2014
Since the last newsletter, the VisualEditor team has mostly worked on performance improvements, image settings, and preparation for a simplified citation template tool in its own menu.


 * In an oft-requested improvement, VisualEditor now displays red links (links to non-existent pages) in the proper color. Links to sister projects and external URLs are still the same blue as local links.
 * You can now open templates by double-clicking them or by selecting them and pressing Return.  This also works for references, images, galleries, mathematical equations, and other "nodes".
 * VisualEditor has been disabled for pages that were created as translations of other pages using the Translate extension (common at Meta and MediaWiki.org). If a page has been marked for translation, you will see a warning if you try to edit it using VisualEditor.
 * When you try to edit protected pages with VisualEditor, the full protection notice and most recent log entry are displayed. Blocked users see the standard message for blocked users.
 * The developers fixed a bug that caused links on sub-pages to point to the wrong location.
 * The size-changing controls in the advanced settings section of the media or image dialog were simplified further. VisualEditor's media dialog supports more image display styles, like borderless images.
 * If there is not enough space on your screen to display all of the tabs (for instance, if your browser window is too narrow), the second edit tab will now fold into the drop-down menu (where the "" item is currently housed). On the English Wikipedia, this moves the "Edit beta" tab into the menu; on most projects, it moves the "" tab. This is only enabled in the default Vector skin, not for Monobook users. See this image for an example showing the "" and "" tabs after they moved into the drop-down menu.
 * After community requests, VisualEditor has been deployed as an opt-in feature at Meta and on the French Wikinews.

Looking ahead: A new, locally controlled menu of citation templates will put citations immediately in front of users. You will soon be able to see the Table of Contents while editing. Support for upright image sizes (preferred for accessibility) is being developed. In-line language setting will be offered as a Beta Feature soon. Looking further out, the developers are also working on support for viewing and editing hidden HTML comments. It will be possible to upload images to Commons from inside VisualEditor.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at VisualEditor/Feedback or by joining the office hours on Monday, 19 May 2014 at 18:00 UTC. If you'd like to get this on your own page, subscribe at VisualEditor for English Wikipedia only or at meta:VisualEditor/Newsletter for any project. Thank you! Whatamidoing (WMF) (talk) 20:23, 23 April 2014 (UTC)

Disambiguation link notification for April 28
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Equipment of the United States Army, you added links pointing to the disambiguation pages M84 and SMAW (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ* Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:57, 28 April 2014 (UTC)

December 2014
You currently appear to be engaged in an edit war&#32; according to the reverts you have made on TACR2 (Range Rover). Users are expected to collaborate with others, to avoid editing disruptively, and to try to reach a consensus rather than repeatedly undoing other users' edits once it is known that there is a disagreement. Please be particularly aware that Wikipedia's policy on edit warring states: If you find yourself in an editing dispute, use the article's talk page to discuss controversial changes; work towards a version that represents consensus among editors. You can post a request for help at an appropriate noticeboard or seek dispute resolution. In some cases it may be appropriate to request temporary page protection. If you engage in an edit war, you may be blocked from editing. Andy Dingley (talk) 21:52, 2 December 2014 (UTC)
 * 1) Edit warring is disruptive regardless of how many reverts you have made.
 * 2) Do not edit war even if you believe you are right.

Disambiguation link notification for December 19
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Paige automobile, you added a link pointing to the disambiguation page Roadster. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ* Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 11:41, 19 December 2014 (UTC)

DTM car articles

 * Saw your post on ANI, thought I'd come and talk with you about it here (I only read the drama boards, and try to avoid posting on them) as someone who is fairly experienced at editing automotive Wiki articles. Since you mentioned the Audi A4 DTM and A5 DTM on ANI, this is what I intend to focus on, particularly as they were written initially by the user you are concerned about. Warning: this is going to be long!
 * Let's start with the A4. Firstly, I should note that User:TheriusRooney (hopefully this will ping them and attract their attention; it probably won't though) last edited the article in April. I have to agree that the level of detail in the specifications is insanely excessive; not to mention completely unreferenced. The nearest thing to a relevant Good Article is Porsche RS Spyder, and as you can see, the level of specification is far lower. Every field in the infobox should be filled wherever the information can be reliably sourced, and none of the more "obscure" technical data needs to be in the main article. A brief overview of the chassis, engine/transmission, braking system and suspension is generally all that is required, unless there is something particularly unique about a major component (e.g., the car's aerodynamics/bodywork, or it has a fan used to suck the car into the track) that needs discussing. This should also be done in a prose format in the main body - exactly like the RS Spyder article has. The design section should also focus on how the car changed through its evolutions; there should be plenty of material on that somewhere, even with the relatively restrictive DTM regulations, since they used the A4 for so long. Now, if I go to the infobox, it is my opinion that there are way too many drivers in there. In my opinion, it should be restricted to perhaps the 4 or 5 most successful drivers; certainly 10 would be a hard limit for me. I don't agree with how the dimensions are presented; they should be in mm, and they should also be converted into inches with a 1 decimal place conversion factor, as is standard practise. There's also a blatant error with the wheelbase, where the numeric value is in cm, but the conversion table is using mm. Some of the sections have a good amount of data, but are light on Wikilinks; some things, like the engine section ("custom-built" isn't necessary, 2xDOHC is basically implied by it being a V-shaped engine), the tyres section (which is literally just for the tyre manufacturers, nothing else). Moving away from the infobox, a summary of the car's performance throughout each of the seasons is necessary, particularly as it won multiple championships!
 * Now, the A5. Most of the above is relevant here as well, although TheriusRooney last edited it at the start of this month. This article is noticeably better, in my opinion, but has most of the same flaws.


 * After that long-winded analysis, let's get back to the user you are concerned about. I believe very strongly that they are acting in good faith; I don't think there's a shred of evidence otherwise, and nor do I think that you were accusing them of being a vandal. I do, however, believe that they aren't quite sure what Wikipedia is for; or that the article they used as a "template" was also overly detailed in the extreme. I know they've never responded to a talkpage message, but neither have you actually tried to contact them to discuss your concerns. I see no major issue with their editing, it just needs improving on in the kind of ways that I've detailed above. This is a collaborative project, after all; if everyone got everything even close to right every time, there'd be much less to do! I see no signs that this user will just go and revert your improvements. Personally, I think you should've taken your concerns to the relevant WikiProject (WP:WikiProject Automobiles) rather than ANI. :) Luke no 94  (tell Luke off here) 21:31, 21 December 2014 (UTC)


 * Thank you for your response Luke and insightful info (as well as your recent edits to the A4/A5 pages). I probably should leave a message on their talk page, but there are many more articles that have User:TheriusRooney's extremely detailed template that need work. Cheers --Stratocaster27''t@lk 17:21, 29 December 2014 (UTC)

4-4-2
4-4-2 is the GM designation; cites were given. Please take your concerns to Talk. Yours, Wikiuser100 (talk) 15:11, 12 January 2015 (UTC)
 * Wikiuser100, I saw the page blank and assumed it to be vandalism (which I shouldn't have done but have seen a lot of page blank vandalism recently). No worries. I'm working on the Buick Riviera article at the moment, which I see you have edited recently as well. --Stratocaster27''t@lk 17:25, 12 January 2015 (UTC)
 * Thank you for your prompt and honest explanation.
 * Like so many others, I had wrongly assumed "442" was the proper designation. It was only while verifying references that I discovered it wasn't a mere inconsistency of use (by some combination of Oldsmobile, the media, and public) but a confusion Olds helped fuel itself (by debuting the car as a 4-4-2, which used vertical bars to separate the numerals on its badging, then dropping the latter in '68).  However, right through the final generation in the '90s, Olds referred to the cars internally and in sales literature as "4-4-2"s.  That was a surprise to me, but is quite definitive.
 * Good luck with the Riviera article; it can still use lots of help. Yours, Wikiuser100 (talk) 17:40, 12 January 2015 (UTC)

ArbCom elections are now open!
Hi, You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 17:01, 24 November 2015 (UTC)