@TheDJ It is correct that the page currently uses a simple image map; however, I had added a Kartographer map for the preview screenshot. A discussion is still occurring regarding whether to implement these maps for cave infoboxes on enwiki, thus explaining why I didn't save the edit. If you'd like to reproduce the issue, change {{Infobox cave to {{Infobox cave/sandbox at the top of the article before entering preview. Sorry for the initial confusion.

Any updates?

@matmarex Now the text isn't going off the screen, but the cursor isn't aligned. Screen capture from Microsoft Edge. The problem is typically caused by turning syntax highlighting from off to on in the middle of an edit.

In T205682#4626173, @Esanders wrote:

My understanding is that {{use dmy dates}} it's a instruction for how to render the dates, not how they are inputted.

In T205149#4623429, @matmarex wrote:

I can't reproduce using Opera 56 (Chromium 69) on Windows 10.

In T205149#4607538, @Izno wrote:

I cannot produce the problem in Firefox 62.0 64-bit on Windows 10. (As noted before, I can with every edit on Firefox Quantum on Android.)

@Izno I'm using Vivaldi (which is built on Chromium). I've also tried it on Microsoft Edge and get the same issue. It doesn't seem to be a browser-specific problem.

@Reedy That would be correct

In T200052#4443298, @Krenair wrote:

In T200052#4443287, @Daylen wrote:

In T200052#4443198, @Krenair wrote:

In T200052#4443195, @Daylen wrote:

The author has only granted permission for it to be used by Wikimedians/the Wikimedia Foundation, so please don't share the link publicly.

Sounds like a pretty surefire way to ensure it's not used by Wikimedians at all.

Sorry, I don't choose the license terms. I'm just following what they stated. The publisher doesn't allow the study to be shared freely. The PDF is only meant to assess security issues, not to cite in articles. In case you would like to take a look at the study, I have emailed you a copy. Cheers, Daylen

I can access it fine personally as I happen to be a member of one of the institutions allowed to use the link in the description. My point is that development decisions generally get made in public, and not all Wikimedians have such access.

In T200052#4443198, @Krenair wrote:

In T200052#4443195, @Daylen wrote:

The author has only granted permission for it to be used by Wikimedians/the Wikimedia Foundation, so please don't share the link publicly.

Sounds like a pretty surefire way to ensure it's not used by Wikimedians at all.

As mentioned by @TheDJ, I linked a copy of the paper to the Wikipedia Weekly and Wikimedia Foundation social media hub private Facebook groups. If you would like to take a look at the study, email me via Meta-Wiki (https://meta.wikimedia.org/wiki/Special:EmailUser/Daylen) and I will share the PDF with you. The author has only granted permission for it to be used by Wikimedians/the Wikimedia Foundation, so please don't share the link publicly.

In T200052#4440124, @MZMcBride wrote:

This is an old topic. If you search this Phabricator installation for "password length", you'll find a bunch of related commits and tasks. There are also wiki pages such as https://www.mediawiki.org/wiki/Requests_for_comment/Passwords and mailing list posts about this.

I think we should be moving in the direction of making it even easier to create wiki accounts, perhaps not even requiring a password to be set at all. We could provide a text input box on the edit screen that allows someone to pick a user name or have one auto-assigned instead of using an IP address. We could support only entering a cell phone number or an e-mail address to make an edit. There are pitfalls to these approaches, naturally, but implementing some of them would likely be an improvement. We want people to edit and contribute to the sites. To this end, we continue to support logged-out editing to promote the culture of fast ("wiki") and easy contributing. In my opinion, encouraging editing and trying to reduce barrier to entry should be our focus, not security theater.

Amazon and Wikipedia aren't really reasonably comparable other than both being Web sites. Nobody uses a credit card to order items to their house off of Wikipedia. :-)

In T192750#4151000, @Reedy wrote:

I'm guessing this would require code signing?

@ksmith mentioned that someone at Microsoft reached out to the Wikimedia Foundation regarding this. I assume the finished project would look something like the image below (I just made using Visual Studio in two minutes, many functions aren't working). If Microsoft is willing to develop the app, I would recommend just having someone at Wikimedia work with them to push the code out through official channels.

Twitter recently updated their Microsoft Store app with a web wrapper. What are your thoughts about doing the same thing with the Windows app?

Twitter recently updated their Microsoft Store app with a web wrapper. What are your thoughts about doing the same thing with the Windows app?

In T174308#3611011, @Mholloway wrote:

Side question: should these replace the old homescreen widgets (i.e., should we disable them for versions for which App Shortcuts are available, and eventually phase them out as we stop supporting legacy versions)?

In T170466#3446951, @Ryasmeen wrote:

In T170466#3446929, @Daylen wrote:

Has the change been merged into the English Wikipedia, as I am still having the problem there?

Not yet, the fix is merged into the beta cluster. It will be released as part of 1.30.0-wmf.10 on English Wikipedia on Thursday, July 20. You can check https://www.mediawiki.org/wiki/MediaWiki_1.30/Roadmap#10 for the schedule.

Has the change been merged into the English Wikipedia, as I am still having the problem there?

In T170466#3439060, @matmarex wrote:

Error message:

SCRIPT438: Object doesn't support property or method 'forEach'
ve.ui.MWSaveDialog.js (188,3)

		body.querySelectorAll( 'link[rel="mw:PageProp/Category"]' ).forEach( function ( element ) {
			categories.push( ve.dm.MWCategoryMetaItem.static.toDataElement( [ element ] ).attributes.category );
		} );

Yes, I can confirm that this is the same issue displaying on my version of Edge

The issue is on Microsoft Edge 40.15063.0.0 on Windows 10 Pro Insider Edition (build 15063).

It would also be nice if disambiguation page links showed up as orange in the preview. This way if you are (for example) editing the real-time ridesharing article on the English Wikipedia, if you add [[Uber]] you will now that you have to add [[Uber (company)|Uber]] instead.