User Details
- User Since
- Aug 21 2017, 11:38 PM (291 w, 5 d)
- Availability
- Available
- IRC Nick
- cooltey
- LDAP User
- Cooltey
- MediaWiki User
- CFeng (WMF) [ Global Accounts ]
Yesterday
Fri, Mar 24
Thu, Mar 23
Thanks for the update, I have updated the ticket description with the APK link.
Wed, Mar 22
Tue, Mar 21
After digging into the code, I noticed that we have a custom card view and it applies all kinds of custom values to border colors and elevation.
Done.
2) When an input field is in the active state, it uses the progressivecolor group for border-bottom
Done.
3) In addition to the border-bottom: input fields have a 0.5dp border-top/left/right in the `border-color group
Fri, Mar 17
Every item you have mentioned has been addressed. Please download the latest APK from the ticket description, thanks!
Tue, Mar 14
Hi @scblr, here are the text styles we have been using in the app, hope these will help you to define the replacement for the new text components in Figma.
Mon, Mar 13
I have noticed the color looks weird in the Sepia theme 🤔
Ok, I’ll keep an eye on that.
Sat, Mar 11
The updates are almost completed and you are welcome to do the first round review of the colors, please download the APK from the ticket description to see the changes.
Fri, Mar 10
Ongoing task
Reduce and update colors in the Android app
Ticket: T330645
Status: working-in-progress
PR: https://github.com/wikimedia/apps-android-wikipedia/pull/3871
Thu, Mar 9
Here are the colors that have been used somewhere else in the app, would you please help me to define the replacements?
Wed, Mar 8
@Seddon Please help to add the correct tag to the team that can do the request, thanks!
Tue, Mar 7
Mon, Mar 6
Fri, Mar 3
After lots of testing and investigation, it looks like the issue is in the OkHttp library that we are using now, which is related to the SocketTimeout issue.
Thu, Mar 2
After further research on the required APIs for this task, it seems like the #3 I have mentioned above cannot fit in the functionality properly.
Wed, Mar 1
Tue, Feb 28
Per discussion in the meeting:
- No extra UI in the editing screen, we should set the cursor at the beginning of the diff text. (if possible).
- If the revision cannot be undone, then pops up a snackbar with a warning message, but still enable the editor for users to edit the content manually.
- We can either check the content if part of the edit of the revision matches the content, or find a possible API to get the status of the current revision vs the undo revision.
What would be the case where the undo action is actually an edit conflict? For example:
https://en.wikipedia.org/w/index.php?title=Treaty_of_Berwick_(1560)&action=edit&undoafter=1141886230&undo=1141925273
Feb 23 2023
Confirmed with @JTannerWMF and created a sub-task for the edge case issue. Now, this parent ticket is able to be closed.
Update: video from Jazmin
https://youtu.be/LxC5_iE31E0
I still can not reproduce the issue. Would it be possible to restart your device and try to reproduce it again? And it would be very helpful if you can provide a video of it. Thanks!
Feb 22 2023
How does the iOS app handle the link which will redirect to the specific talk topic link with the comment anchor? Does the iOS read it and get the redirected URL in the app and then open the talk topic screen?
Feb 21 2023
Feb 18 2023
Hi @scblr
Feb 17 2023
The implementation is completed. You may still see the unchanged behaviors about the tooltips, which relate to another unmerged ticket.
Feb 16 2023
Feb 14 2023
Feb 10 2023
The APK has been updated with the latest design, please download the latest alpha APK from the ticket description.
Feb 8 2023
The research is completed. I have a PR of fixing it and also fixing the zero MB size when importing a list.
@scblr Since there's no alpha APK available for testing, here is a demo video for you to check:
https://youtube.com/shorts/sg2wYTH0xIE