Extension talk:MobileFrontend/2023
Add topicThis page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
If you have a feature request just request it here you'll get a much quicker reply :-) We are also around in #wikimedia-mobile if you want a quicker answer!
If you are trying to replicate behaviour you see on Wikimedia sites, please be sure to read through the configuration options before asking a question here.
Only Use $wgMFAutodetectMobileView & Prevent Other Modifications
[edit]I have two different skins enabled on my wiki. My default one I'd like to show most users, and another one I'd like to show to mobile users.
I like MobileFrontend's $wgMFAutodetectMobileView and the Mobile/Desktop link at the bottom of the page to easily switch between the two, but I don't want any other modifications that the extension does.
I see things can be adjusted, like turning off $wgMFCollapseSectionsByDefault, but that still modifies the code to the allow users to collapse sections.That's just one of many other changes MobileFrontend makes.
Is there a way to disable all the changes the extension does and just use $wgMFAutodetectMobileView? Or is there another extension that might be better for what I'm looking for. 70.160.223.43 (talk) 17:59, 16 July 2023 (UTC)
Style error in Special:MobileDiff
[edit]This topic is moved from Project:Support desk/Flow/2023/08#h-Style_error_in_Special:MobileDiff-20230813061500 at Project:Support desk.
- MediaWiki version: 1.40.0
- PHP version: 8.1.21
- MariaDB version: 11.0.2
- MobileFronted version: 2.4.1
- Minerva version: 2023-06-29
- URL: https://wiki.mcbe-dev.net/
Hello, I am editing wiki on my phone. When I use desktop view, the page for comparing revisions is Special:Diff, which works correctly. But when I switch to mobile view, comparing revisions uses Special:MobileDiff, whose style is broken: The old and new revision are supposed to take up 50% of the screen width, but actually they both take up 100% of the screen width. (Example: Diff, MobileDiff)
I tried to compare revisions in Wikipedia. In Wikipedia, the view of Special:MobileDiff is completely different: There is no 2-column look, instead, the changes are highlighted. Example
Why are the views totally different? Are there any special configurations for Wikipedia, or is this mcbe-dev wiki missing something? TripleCamera2022 (talk) 04:48, 21 August 2023 (UTC)
- Update: Wikipedia is using the inline diff. It has enabled
$wgShowDiffToggleSwitch
, which is because it had updated to 1.41. --The second question is now answered. - I also located the piece of CSS that caused the style error in Special:MobileDiff:
.diff.diff tbody, .diff tr, .diff td { display: block; }
- Finally, the code is located. Module:
mobile.special.mobilediff.styles
. Source code (GitHub). TripleCamera2022 (talk) 09:48, 21 August 2023 (UTC) - Inline diff has nothing to do with
$wgShowDiffToggleSwitch
. To enable inline diff, you need to install wikidiff2 and then add$wgDiffEngine = 'wikidiff2';
to yourLocalSettings.php
. TripleCamera2022 (talk) 06:00, 2 September 2023 (UTC) - I have created T345730 MobileDiff style error when diff engine is php for the style problem. TripleCamera2022 (talk) 15:19, 6 September 2023 (UTC)
Do we need MobileFrontend if there's $wgVectorResponsive?
[edit]Skin:Vector#wgVectorResponsive
Does the same thing but with no extension, doesn't it? 89.149.84.238 (talk) 14:41, 4 September 2023 (UTC)
$wgVectorResponsive
was removed in MediaWiki 1.35; I don't know if it was replaced with anything else. 「ディノ奴千?!」☎ Dinoguy1000 16:07, 4 September 2023 (UTC)- There are a lot of problems with MobileFrontend, especially with managing CSS for consistent display styling since it uses an entirely different skin and ignores "
MediaWiki:common.css
". Unfortunately "$wgVectorResponsive
" doesn't seem to be working correctly for MediaWiki 1.39.4 LTS. - Nicole Sharp (talk) 22:58, 4 September 2023 (UTC)
- @Nicole Sharp:
$wgVectorResponsive
was removed in MW 1.35, as I said in my previous comment. 「ディノ奴千?!」☎ Dinoguy1000 02:39, 5 September 2023 (UTC) - It doesn't seem to have been removed completely but maybe it is just deprecated/unsupported. Enabling "
$wgVectorResponsive
" on MediaWiki 1.39.4 LTS does solve some problems like displaying unsorted lists using bullets instead of periods, but otherwise mismanages image placements so the pages are unreadable. If it was removed completely, then enabling it in "LocalSettings.php
" shouldn't have any effect. I haven't tried using the new Vector 2022 skin yet though so this is just with the Vector Legacy. - Nicole Sharp (talk) 03:48, 5 September 2023 (UTC)
TT
[edit]Typewriter text ("<tt></tt>
") is broken for the Mobile Frontend. This should be fixed in the skin's source code, without needing to set
#mw-content-text tt { font-family: monospace; font-size: large; }
in "MediaWiki:mobile.css
".
Typewriter text is not displayed as monospace when Mobile Frontend is active.
Nicole Sharp (talk) 22:51, 4 September 2023 (UTC)
- Additional suggested CSS for the Mobile Frontend:
- Nicole Sharp (talk) 08:05, 5 September 2023 (UTC)
- Skin:Minerva only supports HTML5 and does not have supported for deprecated tags such as the TT element. I'd recommend using the code element instead if you can. Jdlrobson (talk) 01:16, 7 September 2023 (UTC)
- If it doesn’t support
<tt>
, why doesn’t it just ignore its existence, but rather removes the default, appropriate styling browsers provide? Tacsipacsi (talk) 16:30, 7 September 2023 (UTC) - Because it uses the upstream reset file: http://meyerweb.com/eric/tools/css/reset/
- There's a ticket to stop using that at https://phabricator.wikimedia.org/T205341 and a patch is welcome if anyone wants to provide it. Jdlrobson (talk) 21:35, 7 September 2023 (UTC)
- Editors should use the KBD element (not the CODE element) for "keyboarded text" which would be the closest HTML5 equivalent of "typewriter text". Technically, TT still has a semantic meaning (not just for styling) if it is used to format actual text output from a typewriter but this can still be expressed using KBD (typewriter input) or SAMP (typewriter output) instead. Either way though, a public wiki will likely have many contributors using deprecated tags, so not supporting deprecated tags like "
big
" will break the wiki. HTML5 is designed to be backwards-compatible with HTML 4 so all deprecated tags should remain supported. Nicole Sharp (talk) 12:30, 8 September 2023 (UTC)
Users cannot change the "mobile" skin
[edit]I suggest to set up a new (second) user skin setting page for "skin when viewing on mobile", which skin is then selected when on mobile. Wikinaut (talk) 19:22, 18 October 2023 (UTC)
Changes since 1.35
[edit]I've recently upgraded from 1.35 to 1.40. Unfortunately, the result is that now my main page does not perform the mobile formatting. That is, I'm getting a two-column display. Needless to say, my boxes are defined as "mf-XXX", and everything worked fine up until the upgrade to 1.40. Any idea what might have gone wrong?
PHP 7.4.3 109.186.103.99 (talk) 12:02, 5 November 2023 (UTC)
- So for anyone encountering a similar problem (as evident from previous topics), I resolved this by following the main page layout of helminthictherapywiki. I really appreciate the hard work put into this crucial extension, but some clear documentation on how to actually use it, and how it changes from version to version, would make it a lot more useful and usable. 109.186.103.99 (talk) 15:12, 6 November 2023 (UTC)
- This feature has been removed. While I found no changelog highlighting this change, Mobile Gateway/Mobile homepage formatting has been updated to describe how to do mobile main page formatting in 1.36+. Tacsipacsi (talk) 09:07, 18 November 2023 (UTC)
Cant Collapse Sections on mobile site
[edit]On the mobile version of my wiki the sections are missing the usual arrows at the left hand side of the headings - and while the sections can be expanded, they can’t be closed/collapsed again afterwards. Does anyone know how to fix / try to fix this? Thanks 86.31.127.33 (talk) 21:04, 8 November 2023 (UTC)
- I updated mediawiki to 1.40, updated the Minerva Neue skin and Mobile Frontend extension and it still didn't work. I then Removed the "CollapsibleSections" Extension I'd downloaded and now it works. 86.31.127.33 (talk) 22:34, 20 November 2023 (UTC)
Extension Widgets don't working in MobileFrontend
[edit]also gallery mode="slideshow" not showing on the toggle_view_mobile page. Problem started when i updated mediawiki to 1.40.1 82.200.42.2 (talk) 18:43, 6 December 2023 (UTC)
- Any progress of behavior of Gallery display on MobileFrontend? On my site, it does not showing captions and instead read "License information" along w/ the "Details" button. School4schools (talk) 04:08, 26 February 2024 (UTC)