Can we see the scrollbar in the screenshots? If so that also might confirm that theory about sections not collapsing. In which case something went wrong with our patches that we thought were caching safe and disabled section collapsing on the site which may have caused undesired performance regressions that are worth understanding (and possibly justifying the fact we collapse content by default on mobile).
@ovasileva this should be in blocked on others. We talked about this during last estimation meeting (wednesday) and said all the other icon patches should be done before we consider bumping the size of the icons
@alexhollender blue watchstar should be live on the beta cluster shortly. It will ride train early tomorrow so please let me know today if there are any problems.
I'd expect no reports after the end of this week. If so I think we can safely assume caching and close these tickets. Thanks for letting me know and please do feedback any new OTRS tickets about this issue.
Am closing this bug as most of the issues are solved. The remaining issues are documented in bugs:
T222903, T194453, T233649
Thanks all with the help here in making mediawiki a little more responsive.
What is the URI of the page with that pageid?
Are you able to use the REST_v1 summary endpoint (which is better supported): https://pt.wikipedia.org/api/rest_v1/#/Page%20content/get_page_summary__title_
This is likely a caching issue. We recently moved some code around and had reports that this might not have gone as smoothly as expected.
this bug T233373 may also be relevant - a potential hypothesis is that if sections are not collapsed it causes time to first interactive issues. It's not possible to see in the runs if section collapsing is being enabled or not but the timing would fit.
Fri, Sep 20
Thu, Sep 19
The only module used by Minerva from MobileFrontend now is mobile.startup so this is done.
waiting on some feedback from Ed.
Piotr said he'd take a look
Config only change via a SWAT window. Patch welcomed.
$wgMinervaCustomLogos = [ 'copyright' => 'https://en.m.wikipedia.org/static/images/mobile/copyright/wikipedia-wordmark-en.svg', 'copyright-width' => 100, 'copyright-height' => 18, ];
This only seems to impact beta cluster not production (it works fine on English Wikipedia)
Is this related to recent changes to references preview?
The mw-collapsible code and the sortable code are currently tightly coupled - so enabling sortable requires enabling the other as well. We could modify core to make it possible to do one without the other.
@matmarex looking into this some more the following code in Minerva gets portlet links added where they need to be:
$('.minerva-user-menu .toggle-list__list--drop-down').attr( 'id', 'p-personal' ); $( '#mw-mf-page-left .menu:first-child' ).attr( 'id', 'p-navigation'); $('#page-actions-overflow .toggle-list__list--drop-down').attr( 'id', 'p-tb' );
However Minerva uses a different template for these items, so the do not render properly:
Wed, Sep 18
No longer seeing the JS errors.
I don't know how to fix this. iOS seems to remember where you last clicked and focus any element in that area. Possibly a browser bug?
Possibly need to swat this
I've opened an upstream issue https://bugs.chromium.org/p/chromium/issues/detail?id=1005433 cc @Amire80
I'm giving you 2 options - remove if it's not useful or change the link to something more useful. For this particular task, however I'm saying remove the link to simplify the change (dropping those blue links).
The page issues one is a little tricker - as page issues has a line height of 1.65 so I can't see a way to adjust this icon's position without an arbitrary non-variable based value. Pausing working on this until the other icons are taken care of.
@alexhollender question for you in developer notes
I noted this issue here -T232708#5488613 - for which i've requested RelEng's help as I'm unable to work out what's happened.
There were lots of reports today of the mobile site blanking out - just mentioning this in case there's any relation to this issue (I don't know what could have caused this):