I'm guessing but I think we want just plain {{SITENAME}}. It's listed on the magic words page. {{int:Sitetitle}} refers to MediaWiki:Sitetitle and that page is deleted.

Before writing any patches have a slack conversation outlining your plans to avoid the problems we've been hitting in our refactor work and ensure you have buy in. Make sure to share your work early and check in that everyone understands it.

Here's my initial plan of attack:

Tagging AMC since it's impacted too.

Sorry for the dumb question on a broader topic. Do you know if we should favor {{int:Sitetitle}} or {{SITENAME}}? I see a bunch of references in MobileFrontend and elsewhere to the former but only Timeless appears to use the latter. We have a cool patch from @DannyS712 in MobileFrontend but I'm not sure which we should prefer.

NOTE: tentative deployment date April 30, 2019

@Tbayer, @cscott, @Addshore, @Gilles, @WMDE-leszek, @Smalyshev, @Tarrow, @CKoerner_WMF, @mpopov we're planning to complete the roll out of the "sameAs" page schema changes soon. Please comment if you have any concerns.

I think so, at least for now. T220511 shows a number but it's incorrect. The issue in this bug is that no alert is shown.

Possibly affected by T220979.

All feedback is addressed. Latest changes are up https://readers-web-stephen.wmflabs.org/wiki/User:Hello.

I can repro on emulated Android with sections collapsed on enwiki prod.

Not sure what the heck I'm doing wrong but https://en.m.wikipedia.beta.wmflabs.org/wiki/Qatar shows the Wikipedia:New user landing page when I'm logged in and the Qatar page when I'm logged out:

I tried a number of other pages including local development articles using the content proxy but they seem to be working too. I'm thinking that the most likely issue is either that you're hitting the parsimonious timeout of 3 seconds or an image is failing to download (errors are silently eaten). You may be able to verify the latter by examining the network requests issues after pressing the download PDF button.

I tried to repro this on https://en.m.wikipedia.org/wiki/Barack_Obama but it seems to be working.

All feedback is addressed. Latest changes are up https://readers-web-stephen.wmflabs.org/wiki/User:Hello. Open questions on download icon behavior and toolbar layout to be discussed tomorrow.

Nevermind-- I see you've added it to a related task!

• A deprecated flag is added to mediawiki.template.hogan to ensure existing users move to mediawiki.template.mustache

This seemed like a good idea to me. Was it intentional to remove it from the AC?

I've revised the images and scrolling behavior. The changes are most visible on user pages. E.g., https://readers-web-stephen.wmflabs.org/wiki/User:Hello.

I've moved this to QA per my understanding of super-happy-dev-time discussion. @Jdlrobson, please punt back if you disagree.

Would track any UI you can click on a page in the main namespace. Nothing in search or watchlist. So maybe just top and secondary level UI?

Per our discussion:

@alexhollender, still working through this but the following would help:

This may be improved or fixed by WMDE's work for T215194.

when Echo is not installed it can be used for other things (it falls back to a talk link).

Maybe out of scope for this task but do we need to support a non-Echo configuration?

Sure, works for me.

Regarding iOS: on web browsers (Chrome, Safari, Firefox) swiping rightwards from the left-edge of the screen takes you to the previous page (i.e. it's a back button). This is also the behavior in many other apps.

This is part of the AMC effort and it's parent epic is marked high priority so it may be equally high.

Maybe a similar prompt could appear for citation needed as well? This might work well with Reference Previews.

+Sam who I believe has a personal interest in client-side error reporting.

There's related confusion on which event buses we should use for which purpose too. For example:

Adding @phuedx who I think has a personal interest in client side error reporting. Please feel free to ignore otherwise.

This seems to have been completed entirely by @Esanders. I'm marking it resolved. Thanks @Esanders!!

The section persistence will only work if you are on a mobile resolution and will get confused if you resizethe window.

I didn't know.