Unfortunately, there is no one-size-fits-all. I'd love to make a parser function for ambox templates to revisit the "mess" that is Minerva page issues, but that's a big project.

I recommend avoiding the ambox classes if possible or at least following the guidance on
https://mediawiki.org/wiki/Recommendations_for_mobile_friendly_articles_on_Wikimedia_wikis

Note the page issues handling can be disabled via $wgMinervaPageIssuesNewTreatment = ['base' => false ] so one potential solution is for the templates themselves to be made mobile friendly and for this code to be removed altogether.

In T282984#7098855, @Jdlrobson wrote:

Unfortunately, there is no one-size-fits-all. I'd love to make a parser function for ambox templates to revisit the "mess" that is Minerva page issues, but that's a big project.

I recommend avoiding the ambox classes if possible or at least following the guidance on
https://mediawiki.org/wiki/Recommendations_for_mobile_friendly_articles_on_Wikimedia_wikis

Note the page issues handling can be disabled via $wgMinervaPageIssuesNewTreatment = ['base' => false ] so one potential solution is for the templates themselves to be made mobile friendly and for this code to be removed altogether.

Hi :) Is it possible, when the display of "mobile" versions is turned off, to get to the possibility of opening the "See more" submenu? Perhaps through some CSS class.

Hi :) Is it possible, when the display of "mobile" versions is turned off, to get to the possibility of opening the "See more" submenu? Perhaps through some CSS class.

Not sure I understand the question here, but if the mobile version is turned off (by disabling the feature flag), that would mean no HTML changes on mobile, and no JS/CSS enhancements so we'd just show whatever is in the template (e.g. inline styles/template styles).