The template en:OSM Location map, which used to use a 'Graph:' display-engine before that was turned off, is now back through a combination of <mapframe> and inline css. It is now working well in standard browsers, has minor postioning issues in browser mobile mode, and gets badly mangled within the Android app. The problem is that the template relies on mapframe with a matching overlay <div>, which positions the various graphical and text elements onto the basemap. However the app re-sizes and centers the mapframe basemap, and then appears to use the left edge and the original scale for the overlays, so that they have the wrong origin and the wrong scale. Narrow maps that need little scaling are affected less, but even a 350px map such as that at https://en.wikipedia.org/wiki/Isca_Augusta en:Isca Augusta ends up all over the place, and the map at https://en.wikipedia.org/wiki/Leicester#Geography is not a pretty site. There are currently 5,600 pages with OSM Location maps, so a solution is clearly desirable. If, for example, there was a way of stopping the <mapframe> from re-sizing, and ensuring both items started at the same edge, that might be one option, or (sounds tricky to me) ensuring all the css is scaled to the same as basemap. Any suggestions would be useful. Thanks.
Talk:Wikimedia Apps/Flow
Hello @RobinLeicester,
Could you please share some screenshots with us at any of our support email addresses:
android-support@wikimedia.org
ios-support@wikimedia.org
I have forwarded your inquiry to our engineers and will attach these screenshots to a Phabricator ticket. and send you the link after receiving the screenshots.
Thank you!
Hi there! I've faced with an issue regarding the Chinese hieroglyphics in the app. It's always just in the sans-serif font, whether I changed it to the serif or not. However, it effects only on the Chinese signs itself (the Japanese kanji only, the Korean hancha only, etc.) and those symbols which are at non-hieroglyphic wikis. For example, the switching doesn't work with symbols at an English wikipage with characters, but works at Chinese or Japanese one.
Hello,
I'm Amal Ramadan, a Senior Movement Communications Specialist supporting the mobile apps team. Thank you for reaching out regarding the issue with Chinese hieroglyphics in the app. To assist you better, could you please provide screenshots or a screen recording demonstrating the problem you're experiencing? Please send them to android-support@wikimedia.org OR iOS-support@wikimedia.org based on your device.
This will help us determine if the issue lies within the Android system or if it requires font adjustments within the app.
Thank you.
Hello, In the wikipédia Android app, the link to explain how to make micro contribution is dead https://m.mediawiki.org/wiki/Wikimedia_Apps/Suggested_edits/fr
Thanks for the notice! I’ve opened https://github.com/wikimedia/apps-android-wikipedia/pull/4586 to fix the link when using the app in English; the French version can be fixed after that. (In case you couldn’t find the help page: it’s at Wikimedia Apps/Android Suggested edits/fr.)
The links have been fixed both in English and French; they should be included in the next version.
Have y'all considered adding accessibility functions to the app? In particular TTS would be useful for me. Controls like the app @ voice aloud reader on Android would be awesome.
If not that, then at a minimum, please consider make it possible to toggle citations on and off so I don't have to hear "open parentheses # close parentheses" for every dang citation while using the speak selection tool.
Hello @Mintsenior,
YES, we're actually considering this; this is the main ticket that we're using for updates in implementing text to speech:
https://phabricator.wikimedia.org/T126889, please follow it so you can be updated for any upcoming work we do.
Appreciating your interest and patience as we work to improve the accessibility of the Wikipedia app for you and all users.
Ah. I see. Thank you.
>Abandoned in 2016
I suppose this is as good a motivation to learn to code as any.
If I wanted to propose screen reader compatibility as an alternative stop back measure,
Don't really have coding experience.
Currently, we're engaged in our yearly planning phase, during which big number of features have been proposed' the apps team is evaluating these requests in alignment with the organizational objectives established in collaboration with our communities.
Please subscrie to the ticket I sent eralier to be updated with any actions that will be added to it and I suggest adding the Community Wishlist to your watchlist.
Hi, just wondering, since google has provided no answers: I have over 100 tabs open on the android one, and I accidentally opened another without deleting one. So which tab gets automatically deleted? Is it possible also to find a list of "recently closed tabs"? Thank you in advance.
Hello, @AnyGuy,
If you exceed 100 tabs on Android, opening a new one will cause the oldest tab (indexed as 0) to be automatically deleted.
There are ongoing plans to revamp the tab storage system to accommodate more than 100 tabs. You can find more information about these plans at https://phabricator.wikimedia.org/T353656.
Thank you. Is there also a way to find a recently closed tab?
Actually no, once a tab is closed, it cannot be reopened or accessed again.
When trying to translate the Android app, the fact that I cannot see how the messages appear is annoying and can lead to incorrect translations. Could it be set that all suggested edits become available in the alpha version at the same time as they become translatable, i.e. as soon as the pull request is merged? Of course, this shouldn’t be that way in the release version, but it would help a lot in the alpha version. The alpha version already has some differences, like the ability to do as if I was blocked.
Hello @Tacsipacsi,
Thank you for sharing your feedback with us.
We've gone ahead and created a ticket for your suggestion. If you'd like to stay updated on its progress and any further actions, you can track this ticket on our issue request tracking software, Phabricator, using this link:
https://phabricator.wikimedia.org/T348245
Also, we would like to invite you for our upcoming office hour on October 27th. We will discuss our current and future projects and, of course, to hear your thoughts. You can find all the details on the office hour's page Wikimedia Apps/Office Hours.
Thanks for being part of our awesome community!
Thanks for creating the Phabricator task! Subscribed.
I prefer written communication on Wikimedia, so I don’t plan to attend the office hours; thanks for the suggestion anyways.
On the App there is a row of buttons at the foot of the page. The fourth button is 'Edits'. When I press it I get the '''Edits''' page, with a couple of totals at top left. '4016 Contributions' is reasonable, being close to my total on the xtools 'Edit counts' page. But where does '2697 Views' come from, or what sort of views does it refer to? I can't see any similar total on 'Edit counts'.
Hello @Verbarson,
Thank you for reaching out and for your inquiry regarding the 'Edits' page on the Wikipedia mobile app. We appreciate your interest in understanding the statistics displayed there.
The '2697 Views' you see on the 'Edits' page of the app refers to the total number of page views for articles you have edited or contributed to.
It reflects how many times the articles you've edited or contributed to have been viewed by other users; the number of page views (in the last 30 days) of the last 10 articles to which you have added Wikidata descriptions.
If you have any further questions or if there's anything else you'd like to know about the app's features or statistics, please feel free to ask.
When I use the Wikipedia app (on Android) there is a bottom-border menu that includes a hamburger button labelled 'More'. When I select this, it presents six options, starting with my own user page, and finishing with 'Donate'. Of these six, four are wikilinks that open in the app, and 'Donate' is a URL since it opens a page outside Wikipedia. What annoys me is that the first link, to my own user page, is also a URL, so it opens in a browser. Why is this? If I want to use the browser interface, I can decide that for myself, but if I've chosen to use the app, why would it send me over to the browser?
I know that can get there via my user talk page in one extra click, but...
Not a major issue, just a persistent niggle.
Hello @Verbarson,
Thank you for sharing your feedback about the behavior of the 'More' menu in the app. We understand your concern regarding the user page link opening in a browser instead of within the app.
I wanted to let you know that your suggestion has been taken seriously, and we value your input in enhancing the app's user experience. To address this issue, I have created a ticket to investigate and consider implementing a solution that keeps the user page link within the app, providing a seamless browsing experience.
Thank you for taking the time to share your thoughts, and if you have any further suggestions or encounter any other issues, please don't hesitate to reach out. Your input is valuable to us.
Hello @Verbarson, with another update!
We appreciate your patience and wanted to inform you that the issue you raised regarding the 'More' menu behavior is currently under active development.
We're working diligently to ensure that the user page link will open within the app, offering a smoother experience.
Expect this enhancement to arrive very soon.
Hello App-Team,
thank you for the App, but I have to say that there are some things that dont work good. It would be great to fix it. To me I wanna to say that I am mainly in the German Wikipedia and my English isnt perfect.
1) The App shows the Articles of the day, in German: "Artikel des Tages" Thats ok, but you use the first image in the article and not the image who is on the site I linked. Why? Please use the images the users say: "That is for Artikel des Tages" the better picture than the first. For example: Focke-Wulf Ta 154 was Artikel des Tages. On the site there was blak/white the image Commons: File:Profil_Focke-Wulf_Ta_154_II.png and not the first. But on the App there was the first image in the article. Its ok that the picture is the first in the article, but the App said: Oh look there is a great article and here is a picture with an Swastika. That isnt cool. Its ok thats on the article, but we dont have to show this picture wenn people are not directly intereted.
2) In the German Wikipedia there are „gesichtete Versionen“, so there Accounts with the ability to „sight“ on the one hand. On the other hand there are accounts who cannot spam or make vandalism. But on the App there is always the newest version, but not the newest sighted version. Please show only „gesichtete Versionen“.
3) All the tim I am logged in. Often I am in the case that I want to look for the watchlist, but when I touch at the field „Beobachtungsliste“ than it dont work. My workaround is to touch on a article to open the article, than go back and than go to the watchlist. I have no idea why, but thats my reality.
Thank you that I can give my feedback. It would be very great when you fix these 3 points :) PS: I had to deleted some links because ⧼abusefilter-warning-linkspam⧽ --Fan-vom-Wiki (talk) 16:17, 9 June 2023 (UTC)
Thank you for your feedback and for bringing these concerns to our attention. We appreciate your support and understanding as we work towards improving the Wikipedia app experience. I would like to address each of your points individually:
- Regarding the "Artikel des Tages" (Article of the Day) feature, we understand your concern about the displayed images. The images used in the app are generally the first images found within the articles. There’s a ticket on our software tracking system, Phabricator, that’s related to your suggestion. We strive to provide a visually engaging experience while maintaining the integrity and appropriateness of the content. However, we acknowledge the importance of considering user preferences when it comes to selecting images for this feature. Please check this link on Wikipedia: Featured article criteria to know more about how and why this happens.
- We are aware of the existence of "gesichtete Versionen" (sighted versions) in the German Wikipedia; you can check this ticket on Phabricator for more detailed information.
- We apologize for the inconvenience you have experienced when accessing the watchlist on the app. We understand the frustration caused by the described issue and appreciate you sharing your workaround. Could you kindly let us know which version of the app you are using, whether it is the Android or iOS version?
We value your feedback, as it helps us identify areas for improvement and prioritize our efforts accordingly. Rest assured, we are committed to enhancing the app and delivering a better user experience. Your input is invaluable in this process, and we thank you for taking the time to share your thoughts and suggestions. If you have any further questions or additional feedback, please don't hesitate to reach out. We appreciate your comments and feedback.
@ARamadan-WMF There is no watchlist on iOS – or is it now?
Hello @Vincenzo1492,
Thank you for your inquiry. As of now, the watchlist feature is being finalized for iOS. We understand its importance and are actively working to bring this functionality to the Wikipedia app on iOS.
To stay updated and informed about the progress of this feature, you can follow the project page on Mediawiki, where you can find comprehensive information and updates.
We appreciate your patience and look forward to delivering a more enhanced experience with this upcoming feature.
The update on Wikimedia Apps/Team/IOS pls is needed for the latest input. Kindly push those for fuzzy please.
I think that happened right after you wrote.