Android uses the section id for determining which section is being edited. We'll be happy to see a noedit parameter to prevent editing of sections that are transcluded or otherwise weird.
Tue, Apr 17
No longer true in latest alpha.
Fri, Apr 13
This needs much more detail to be actionable:
Thu, Apr 12
@RHo Looks like there's a technical limitation here:
When you highlight text and "share" it using the standard Android picker, it's shared as plain-text and cannot be "filtered" in the same way that links are filtered (where our app can subscribe to receive links only from *.wikipedia.org). Therefore we can only create another catch-all handler (similar to our current "Search Wikipedia" handler) that takes any arbitrary text and assumes that it's a title to be added to a reading list.
patch already in place: https://gerrit.wikimedia.org/r/425848
Tue, Apr 10
Closing in favor of T191337
Fri, Apr 6
Thu, Apr 5
@dr0ptp4kt Yes, most likely. The release notes of the Support Library often don't contain the "full" list of bugs fixed, so it's difficult to know which update is responsible for this particular inconsistency.
Thanks, @Mholloway . As a stopgap solution for this issue, I would recommend against setting the device's date two years into the future.
The Feed content endpoints seem to be returning "valid" content for dates in the far distant future:
Wed, Apr 4
OK cool! I got confused by the wording of "CSS for each page regardless of site", but it sounds like we're on the same page.
The user is welcome to un-split the screen (or change the split width) to see the preview.
You are correct; this is not specific to the app.
Generally I'm in favor of moving away from bundling CSS in the apps altogether, or perhaps go back to the apps' old original strategy of bundling a fallback CSS collection, but then periodically refreshing it from the live site in the field. This could apply to both site-specific and even general (minerva) CSS.
Tue, Apr 3
@cooltey Since you're the best person to understand the root of this issue, could you possibly:
- Step through the code and understand why it's failing
- Paste any logcat errors that are appearing
- If the issue turns out to be simple enough, fix it?
Mon, Apr 2
cc @RHo ^ I've got a patch standing by ;)