Thewolfchild (talk | contribs) (→Question re: desktop vs mobile: new section) |
(→Question re: desktop vs mobile: fix very broken and inaccessible syntax) |
||
Line 196: | Line 196: | ||
When accessing Wikipedia (WP) on a [[smartphone]], but via that device's own [[Mobile browser|internet browser]] (and not via [[Help:Mobile access#Official mobile version|the WP app]]), WP always opens up in "mobile view", and I then need to switch it to "desktop mode" (my personal preference), and sometimes this needs to be done repeatedly. |
When accessing Wikipedia (WP) on a [[smartphone]], but via that device's own [[Mobile browser|internet browser]] (and not via [[Help:Mobile access#Official mobile version|the WP app]]), WP always opens up in "mobile view", and I then need to switch it to "desktop mode" (my personal preference), and sometimes this needs to be done repeatedly. |
||
And speaking of "preferences" and using the search function on the "Preferences" page, I used "desktop" as a keyword for a search, but I only found one entry, that was under:<p> |
And speaking of "preferences" and using the search function on the "Preferences" page, I used "desktop" as a keyword for a search, but I only found one entry, that was under:<p> "{{blue|Gadgets}}"</p><p> "{{blue|Testing and development}}"</p><p> □ "{{blue|Mobile sidebar preview: show page in mobile view while browsing the desktop site (Vector skin only)}}"</p> |
||
So, with all that said, my question is: is there any setting in the my account preferences (or by any other means) that can be used to make it so that when I access WP, via a smartphone's browser, the default can be set to "desktop mode" ''instead of'' "mobile view"...? Thanks & Cheers - [[User talk:Thewolfchild|<span style="color:black">w<span style="color: red;">o</span>lf</span>]] 04:31, 16 March 2023 (UTC) |
So, with all that said, my question is: is there any setting in the my account preferences (or by any other means) that can be used to make it so that when I access WP, via a smartphone's browser, the default can be set to "desktop mode" ''instead of'' "mobile view"...? Thanks & Cheers - [[User talk:Thewolfchild|<span style="color:black">w<span style="color: red;">o</span>lf</span>]] 04:31, 16 March 2023 (UTC) |
Revision as of 04:58, 16 March 2023
Policy | Technical | Proposals | Idea lab | WMF | Miscellaneous |
- Table of contents
- First discussion
- End of page
- New post
If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.
Font peculiarity
I noticed a peculiarity in the "Komika Axis" font, and I'm not sure if the question can be answered here, but here's my question. Komika Axis is an all-caps font (both a and A would resemble A, both b and B would resemble B, etc.), logically the eszett (ß) should be displayed as SS, ß, or ẞ. Unexpectedly, it's displayed as ⅔, a character which ß has no resemblance nor connection to. Even more unexpectedly, the actual Unicode character "⅔" is not supported by the font. To summarize the concept: Character A is being wrongly displayed by a font as Character B, while Character B, on the other hand, is not even supported by the font. It just seems weird, and I don't know if it had to do with the mix-up of the way codepoints were assigned in the creation of the font, or if there is another reason. Does anyone know reasons to something like this? Btw you can look at User:Cmnpt/sandbox to get an idea of what I'm taking about. Cmnpt (talk) 04:17, 10 March 2023 (UTC)
- Both characters render correctly for me. I see the eszett in the first example and the 2/3 character in the second example. As the edit notice for this page recommends, tell us what browser you are using. Also try other browsers if possible. – Jonesey95 (talk) 05:54, 10 March 2023 (UTC)
- Can you see both characters correctly in Komika Axis font? Because it appears to be a problem with the font, I usually can see both characters correctly, but they are mixed up in this particular font. Can you take a screenshot of what you see on your side? My current browser is Google. Thank you! Cmnpt (talk) 06:03, 10 March 2023 (UTC)
- Yes, I see them in that font. See the screen shot to the right. This was taken in the Brave browser, latest version, on Mac OS. I do not have the Komika Axis font installed. – Jonesey95 (talk) 07:14, 10 March 2023 (UTC)
- Fonts are rendered by your own computer, not by Wikipedia which just sends HTML with the number of the character and name of the font. If you don't have the font then a fallback font is used. Here is "a A ß ⅔" in Komika Axis: "a A ß ⅔". I don't have Komika Axis and my fallback font works so apart from minor font differences, I see the same characters in both cases, including a small "a" which should have looked like capital "A" in Komika Axis. PrimeHunter (talk) 10:22, 10 March 2023 (UTC)
- Can you see both characters correctly in Komika Axis font? Because it appears to be a problem with the font, I usually can see both characters correctly, but they are mixed up in this particular font. Can you take a screenshot of what you see on your side? My current browser is Google. Thank you! Cmnpt (talk) 06:03, 10 March 2023 (UTC)
- Seems like a bug with the font. Nardog (talk) 09:56, 10 March 2023 (UTC)
- Thank you, that's what I thought the issue was. This isn't the first time I've seen something like this, so I was wondering, what seems to be the main reason that causes these codepoint mix-ups? Are the two characters related in codepoints somehow, or does it have to do with an error in assignments to the display of each character in a font? Thank you! Cmnpt (talk) 20:25, 10 March 2023 (UTC)
- This forum is for help with English Wikipedia technical aspects. I don't think we can help you any further on that line of questioning. Izno (talk) 20:41, 10 March 2023 (UTC)
- In hexadecimal Unicode, ß is
00DF
: ß. ⅔ is2154
: ⅔. I don't know how Komika Axis mixed them up. Computing questions unrelated to Wikipedia can be asked at Wikipedia:Reference desk/Computing. PrimeHunter (talk) 14:09, 11 March 2023 (UTC)
- In hexadecimal Unicode, ß is
- This forum is for help with English Wikipedia technical aspects. I don't think we can help you any further on that line of questioning. Izno (talk) 20:41, 10 March 2023 (UTC)
- Thank you, that's what I thought the issue was. This isn't the first time I've seen something like this, so I was wondering, what seems to be the main reason that causes these codepoint mix-ups? Are the two characters related in codepoints somehow, or does it have to do with an error in assignments to the display of each character in a font? Thank you! Cmnpt (talk) 20:25, 10 March 2023 (UTC)
Shortcuts box messes up cell phone view in narrow portrait orientation
See: Template talk:Wikipedia how-to#Shortcuts box messes up cell phone view in narrow portrait orientation. --Timeshifter (talk) 10:31, 10 March 2023 (UTC)
- It is because the Module:Message box family is not responsive. There's been some ideas on that, but none are currently deployed. —TheDJ (talk • contribs) 11:53, 10 March 2023 (UTC)
- As for ideas, it's less ideas and more "I have to work through the slog of any/every other box that might possibly be doing something really really bad with assuming the structure of message boxes. Right now I know of just the templates including the relevant TemplateStyles directly (among them the mess that is WikiProject banner), but there may be others. Izno (talk) 20:43, 10 March 2023 (UTC)
- @Izno maybe something like this can help here ? —TheDJ (talk • contribs) 12:29, 10 March 2023 (UTC)
- @TheDJ I'd rather just throw some caution to the winds and nowrap the links in the shortcut box in TemplateStyles until mbox is actually responsive. Not surprised this showed up as quick as it did. :) Izno (talk) 20:38, 10 March 2023 (UTC)
- That isn't the problem here though. Its that the shortcuts squeeze the mbox-text content of the ombox. Mostly because of text inflation algo blowing up the 'expected' size of imageright. —TheDJ (talk • contribs) 15:55, 13 March 2023 (UTC)
- @TheDJ, I am aware it's not the issue. I am suggesting a workaround for the time being in Module:Shortcut/styles.css, which already has some CSS for the special case where it's in an mbox. We can either directly override break-word on it or apparently apply white-space: nowrap according to my test. We knew this would be a special case when I raised it on the task a couple weeks ago. Izno (talk) 20:46, 13 March 2023 (UTC)
- That isn't the problem here though. Its that the shortcuts squeeze the mbox-text content of the ombox. Mostly because of text inflation algo blowing up the 'expected' size of imageright. —TheDJ (talk • contribs) 15:55, 13 March 2023 (UTC)
- @TheDJ I'd rather just throw some caution to the winds and nowrap the links in the shortcut box in TemplateStyles until mbox is actually responsive. Not surprised this showed up as quick as it did. :) Izno (talk) 20:38, 10 March 2023 (UTC)
- I've made some modifications so that the shortcut clears the message and thus no longer squeezes the message. —TheDJ (talk • contribs) 12:30, 14 March 2023 (UTC)
- I've reverted. @TheDJ, you gotta engage with what I'm suggesting. If you don't like that, that's fine, but I think your path is wrong. Izno (talk) 15:54, 14 March 2023 (UTC)
- I must have not understood your suggestion in that case ? —TheDJ (talk • contribs) 20:58, 14 March 2023 (UTC)
- @TheDJ, in Module:Shortcut/styles.css, one of:
.mbox-imageright .module-shortcutboxplain a { word-break: normal }
.mbox-imageright .module-shortcutboxplain a { white-space: nowrap }
- I'm inclined to the former. Izno (talk) 21:19, 14 March 2023 (UTC)
- I was just in the process of adding a screenshot, because i think we are talking about two completely different things.. —TheDJ (talk • contribs) 21:23, 14 March 2023 (UTC)
- Ok, yes, that's not the same issue. However, hacking around it by forcing a table into display: block is not the solution. If we want to fix it, let's actually fix it. I would appreciate help. I've now mentioned the correct fix in no less than about a dozen places and I'm tired of saying it. Izno (talk) 21:28, 14 March 2023 (UTC)
- I was just in the process of adding a screenshot, because i think we are talking about two completely different things.. —TheDJ (talk • contribs) 21:23, 14 March 2023 (UTC)
- @TheDJ, in Module:Shortcut/styles.css, one of:
- I must have not understood your suggestion in that case ? —TheDJ (talk • contribs) 20:58, 14 March 2023 (UTC)
- I've reverted. @TheDJ, you gotta engage with what I'm suggesting. If you don't like that, that's fine, but I think your path is wrong. Izno (talk) 15:54, 14 March 2023 (UTC)
TheDJ and Izno. How about changing Template:Wikipedia how-to so that the shortcuts are just placed in a new line at the bottom of the box. No one would have to do anything. The template would do all the work of changing the location of the shortcuts.
{{Wikipedia how to|WP:SORT|WP:TABLESORT}} would end up as this line at the bottom of the box:
- Shortcuts: WP:SORT, WP:TABLESORT. --Timeshifter (talk) 21:38, 10 March 2023 (UTC)
- @Timeshifter because this pattern of placing shortcut boxes in
|imageright=
of a message box is not exclusive to that template. Please be patient while we work on the problem. Thanks. Izno (talk) 21:39, 10 March 2023 (UTC)- TheDJ and Izno. There is more discussion from others at Template talk:Wikipedia how-to. --Timeshifter (talk) 02:18, 13 March 2023 (UTC)
Global RfC filled to enable global abuse filters on large Wikimedia projects by default
Hello!
On Meta-Wiki, a set of global abuse filters is maintained by Meta-Wiki's administrators and the stewards. Global abuse filters are a powerful tool designed to fight against long-term abusers that operate cross-wiki. It is especially useful (and often irreplaceable by other means) when a cross-wiki LTA starts to rapidly change IP addresses (when that happens, regular blocks are significantly limited due to the IP hopping).
As of today, all small/medium Wikimedia projects (as-determined by number of articles) are automatically subscribed to global abuse filters. They are not, however, enabled on several Wikimedia projects classified as large (except several large Wikimedia projects who opted-in, such as Wikidata). This makes it possible for global long-term abusers to vandalize a project with no global filters enabled, which makes it significantly more difficult for the Stewards to fight against the abuse.
By this message, I'd like to let you know I submitted a global RfC (request for comments), where I propose enabling global abuse filters on large Wikimedia projects as an opt-out feature. This change will make global abuse filters an even more effective tool for combating long-term abuse at the global level. Please feel free to participate in the discussion, which happens at Meta-Wiki.
Thank you for your time.
Sincerely,
--Martin Urbanec (talk) 17:15, 12 March 2023 (UTC)
Confused about s2cid parameter
I originally asked this question at the Help Desk, but another user suggested I come here.
About a week ago, I added a documented parameter (s2cid
) to the TemplateData of {{Citation/doc}}. Today I noticed an error message, |s2cid=
is not a valid parameter. Confused, I searched the Citation Module for any mention of it, and found nothing. My memory may be faulty, but I remember finding this elusive parameter in the Module before. I don't understand Lua, so the answer may be hiding in plain sight. I was going to remove the parameter from the TemplateData, assuming I had made a mistake, but tested it first, to confirm it was not, in fact, a "valid parameter." It worked: Climatic influences on the genetic structure and distribution of the common vole and field vole in Europe, S2CID 55192908, and the parameter is in use in a number of pages (e.g., El Cid).
So should the s2cid parameter be removed from the TemplateData on {{Citation/doc}}?
Thank you in advance,
Edward-Woodrow (talk) 18:24, 12 March 2023 (UTC)
- @Edward-Woodrow: Where do you see the error message? Give steps to reproduce if you cannot post a link where it's displayed now. PrimeHunter (talk) 19:57, 12 March 2023 (UTC)
- @PrimeHunter: The error message has disappeared- I assume whatever oddity there was has been fixed. Edward-Woodrow (talk) 20:02, 12 March 2023 (UTC)
- You probably saw it at Template:Citation/doc#TemplateData. It was fixed by [1]. PrimeHunter (talk) 20:14, 12 March 2023 (UTC)
- @PrimeHunter: Yes, thank-you. Edward-Woodrow (talk) 20:18, 12 March 2023 (UTC)
- @Edward-Woodrow: For future ref, problems with any citation template (or doc) should be reported at the talk page for that template; most of them redirect to Help talk:Citation Style 1 which has more than 450 watchers. --Redrose64 🌹 (talk) 23:52, 12 March 2023 (UTC)
- @PrimeHunter: Yes, thank-you. Edward-Woodrow (talk) 20:18, 12 March 2023 (UTC)
- You probably saw it at Template:Citation/doc#TemplateData. It was fixed by [1]. PrimeHunter (talk) 20:14, 12 March 2023 (UTC)
- @PrimeHunter: The error message has disappeared- I assume whatever oddity there was has been fixed. Edward-Woodrow (talk) 20:02, 12 March 2023 (UTC)
Issue with images in Velociraptor
In the Velociraptor article, the images File:Velociraptor Restoration.png and File:Velociraptor_mongoliensis.jpg are showing images of a Jurassic World velociraptor, rather than the actual image. However, when the images are clicked on, the proper image is shown. According to the talk page, this issue only seems to occur for some users. Purging the page didn't seem to fix the issue. Does anyone know why it's showing up like this? Thanks in advance! -- KomradeKalashnikov (talk) 23:38, 12 March 2023 (UTC)
- Press CTRL+F5 maybe? To make sure you're clearing your cache Darkwarriorblake / Vote for something that matters 23:39, 12 March 2023 (UTC)
- I'm using Chrome on mac, so I'm not able to do CTRL+F5. However, I have tried shift+refresh, as well as manually clearing the cache in Chrome settings. -- KomradeKalashnikov (talk) 23:46, 12 March 2023 (UTC)
- The correct image displays for me, but click on it to generate the preview and it's the Jurassic one. Then click "more details" and the correct version loads on Commons. It looks to be a problem stemming from a vandal who overwrote the Commons file with the version from Jurassic World. [2] The Jurassic version got deleted from the history, yet somehow is still rendering in some cases. Home Lander (talk) 01:31, 13 March 2023 (UTC)
- @KomradeKalashnikov: See WP:BYPASS#Google Chrome for various techniques, some of which may be more effective than others. --Redrose64 🌹 (talk) 15:04, 13 March 2023 (UTC)
- Ok, that seems to have fixed File:Velociraptor Restoration.png, but File:Velociraptor mongoliensis.jpg is still showing up as the Jurassic World one, not the actual image. -- KomradeKalashnikov (talk) 15:38, 13 March 2023 (UTC)
- I executed a purge of both file pages on Commons and on en.wp. Hopefully that bypasses the cached files. I suspect when the versions were originally deleted, some events missed eachother an the the thumbnail delete wasn't properly completed. Or it is a datacenter specific issue, that we have seen more often. —TheDJ (talk • contribs) 15:51, 13 March 2023 (UTC)
- That appears to have worked. Thanks! -- KomradeKalashnikov (talk) 16:00, 13 March 2023 (UTC)
- I'm using Chrome on mac, so I'm not able to do CTRL+F5. However, I have tried shift+refresh, as well as manually clearing the cache in Chrome settings. -- KomradeKalashnikov (talk) 23:46, 12 March 2023 (UTC)
Tech News: 2023-11
MediaWiki message delivery 23:17, 13 March 2023 (UTC)
SVG and prefers-color-scheme
For testing purposes, I've uploaded a revision of File:Northern Quest Resort & Casino (logo).svg that uses CSS @media (prefers-color-scheme: dark)
to render the logo in a reverse format when used in a dark setting. Sadly this doesn't work here yet, but if SVG is served directly in the future this would work with a functional dark mode. I'm debating creating a template and possibly a tracking category for editors to mark images that support dark/light modes as such (this would also help future editors who may accidentally remove such functionality if they run it through a tool that doesn't understand prefers-color-scheme
). I feel like it's worth it to future-proof images, especially since for some vector logos it's more than simply turning a dark color white. Is there already a template/category for marking SVG files as supporting this? Any thoughts/feedback on this? —Locke Cole • t • c 04:50, 14 March 2023 (UTC)
- Just for follow-up, I've created Category:SVG images that support dynamic color schemes and {{SVG supports dynamic color schemes}} to mark images that support this. Probably something a bot could check for and tag automatically too (ideally MediaWiki would detect this automatically at some point). —Locke Cole • t • c 15:53, 15 March 2023 (UTC)
Browser/OS-specific issues with MediaWiki:GeoHack.js
Please could anybody with Linux and/or Chrome installed check out Template talk:GeoTemplate#Map jumps upon first zoom click. Since this is a problem with MediaWiki:GeoHack.js and not with Template:GeoTemplate, I have raised the matter at MediaWiki talk:GeoHack.js#Map jumps upon first zoom click and it's probably best to discuss potential solutions on that page. --Redrose64 🌹 (talk) 09:06, 14 March 2023 (UTC)
Help with lint error
Hello! Can someone with experience in lint errors help me fix a lint error in my homewiki? I have the LintHint gadget active and it tells me there's a lint error in our main page (w:sq:Faqja kryesore) but it's been 2 days hunting it down and I can't really figure out where it is exactly coming from. (It must be transcluded from some other place, not exactly in the main page.) - Klein Muçi (talk) 10:02, 14 March 2023 (UTC)
- sq:Stampa:Lexo is outputting an extra
</span>
.{{#switch:...}}
and<span>...</span>
are misnested (}}</span>
should be</span>}}
). Nardog (talk) 10:23, 14 March 2023 (UTC)- Nardog, thanks a lot! Might if I ask how you found out? Or just plain eye analysis? I was led up until that template with the aforementioned gadget's help but that's where I stopped. — Klein Muçi (talk) 10:32, 14 March 2023 (UTC)
- I ran LintHint on ExpandTemplates, then located the responsible template by repeating the process of previewing the source with
{{
replaced with{{subst:
a couple times. Nardog (talk) 10:37, 14 March 2023 (UTC)- Nardog, thank you! — Klein Muçi (talk) 10:42, 14 March 2023 (UTC)
- I ran LintHint on ExpandTemplates, then located the responsible template by repeating the process of previewing the source with
- Nardog, thanks a lot! Might if I ask how you found out? Or just plain eye analysis? I was led up until that template with the aforementioned gadget's help but that's where I stopped. — Klein Muçi (talk) 10:32, 14 March 2023 (UTC)
Thumbnails not generating
I've noticed that thumbnails across several pages are failing to generate. This one that I placed on an article this morning took about an hour before I got anything other than a broken image, and this one that I just placed is still broken as I type this. Opening those images gives me:
Error Our servers are currently under maintenance or experiencing a technical problem. Please try again in a few minutes. See the error message at the bottom of this page for more information. If you report this error to the Wikimedia System Administrators, please include the details below. Request from [redacted] via cp1078 cp1078, Varnish XID 51659240 Upstream caches: cp1078 int Error: 404, Not Found at Tue, 14 Mar 2023 22:10:12 GMT
--Ahecht (TALK
PAGE) 22:11, 14 March 2023 (UTC)
- Probably phab:T331820. Izno (talk) 22:53, 14 March 2023 (UTC)
No style sheet on preferences page?
My common.css includes:
#pt-logout { display: none; }
to hide the logout link. Special:Preferences still shows the link. Any idea what's going on there? -- RoySmith (talk) 15:19, 15 March 2023 (UTC)
- @RoySmith: I've read somewhere that this is intended. All your customised js/css is skipped when loading the preferences page, so that the page is safe to use even if the js/css has been damaged. -- John of Reading (talk) 15:47, 15 March 2023 (UTC)
- Hmmm, auto safe mode. That actually makes a lot of sense, thanks. -- RoySmith (talk) 15:51, 15 March 2023 (UTC)
- There are a few special pages that have disallowUserJs, etc on them, on purpose. Part of it is for user access resiliency, part for user security. — xaosflux Talk 16:02, 15 March 2023 (UTC)
- We have the default false for mw:Manual:$wgAllowSiteCSSOnRestrictedPages so sitewide css is also skipped in preferences. It appears there isn't even a MediaWiki option to allow it for js. PrimeHunter (talk) 18:36, 15 March 2023 (UTC)
- There are a few special pages that have disallowUserJs, etc on them, on purpose. Part of it is for user access resiliency, part for user security. — xaosflux Talk 16:02, 15 March 2023 (UTC)
- Hmmm, auto safe mode. That actually makes a lot of sense, thanks. -- RoySmith (talk) 15:51, 15 March 2023 (UTC)
You are invited to join the discussion at Wikipedia:Village pump (idea lab) § Tool for bypassing redirects in see also sections. {{u|Sdkb}} talk 19:42, 15 March 2023 (UTC)
Script or tool for finding duplicate citations
Is there a tool or script for checking an article for duplicated citations, that will, if any are located, give an option to group those references using <ref name=>
? Nthep (talk) 19:51, 15 March 2023 (UTC)
Vector 2022: possible "overflow to the left" in tables with images
Using a table to place images next to each other can result in an "overflow to the left" (overlapping the contents table), which would not happen under Vector 2010. I tried to demonstrate this in my sandbox. Is this a bug or a feature? Kallichore (talk) 00:16, 16 March 2023 (UTC)
- You are not giving the renderer any choice. You created a table that is four cells wide, and each cell contains a thumb-sized image. If four thumb-sized images are wider than the content column, the images will overlap the left sidebar or the right sidebar. If you want the images to stay within the content column for all viewers, use
<gallery>...</gallery>
tags or a similar flexible image display mechanism. – Jonesey95 (talk) 00:34, 16 March 2023 (UTC) - As per Jonesy, plus: the table has the (obsolete)
align=right
attribute, which forces the right-hand edge of the table to be within the pane; consequently if the table is wider than the pane, it's left-hand edge must necessarily project outside the pane. --Redrose64 🌹 (talk) 00:36, 16 March 2023 (UTC)- Thanks, I agree that the solution with gallery is better than the “table version”. So this is an example for the following advice from this FAQ: “Q: Some tables and templates don’t fit within the limited width. A: We should make sure that all of our content is as responsive as possible to accommodate all visitors.” --Kallichore (talk) 00:59, 16 March 2023 (UTC)
Question re: desktop vs mobile
When accessing Wikipedia (WP) on a smartphone, but via that device's own internet browser (and not via the WP app), WP always opens up in "mobile view", and I then need to switch it to "desktop mode" (my personal preference), and sometimes this needs to be done repeatedly.
And speaking of "preferences" and using the search function on the "Preferences" page, I used "desktop" as a keyword for a search, but I only found one entry, that was under:
"Gadgets"
"Testing and development"
□ "Mobile sidebar preview: show page in mobile view while browsing the desktop site (Vector skin only)"
So, with all that said, my question is: is there any setting in the my account preferences (or by any other means) that can be used to make it so that when I access WP, via a smartphone's browser, the default can be set to "desktop mode" instead of "mobile view"...? Thanks & Cheers - wolf 04:31, 16 March 2023 (UTC)