Page MenuHomePhabricator

Special pages should open in Safari
Closed, InvalidPublic

Description

Screenshot

See screenshot. I guess this is because it goes to Special:BookSources, and special pages don't "exist" according to the mobile app?


Version: Alpha
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=39906

Attached:

2014-04-15_15.01.23.png (960×640 px, 113 KB)

Details

Reference
bz63973

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:08 AM
bzimport set Reference to bz63973.
bzimport added a subscriber: Unknown Object (MLST).

Changed title to describe the problem more accurately.

Should we just bump these to the browser?

@Legoktm can you confirm this is an issue for the current iOS app? The screen shot is for the app that is no longer available for download?

It now shows an error: "The operation couldn't be completed. (ArticleFetcher error 666.)"

Re-checked with 5.0.0.534 on iPad iOS 9.1

  1. no more messages such as

"The page you requested does not exist."
"The operation couldn't be completed. (ArticleFetcher error 666.)"

  1. Search for Special:BookSources - a blank page is displayed that can be Saved and it's also will be displayed in Recent
  2. Following ISBN links from e.g. 'Aaron Hillegass' - Bibliography also displays blank pages that can be saved.
  3. Such ISBN links (e.g. https://en.wikipedia.org/wiki/Special:BookSources/032194206X) are valid links in wiki and in Mobile.

@JMinor Should this be fixed as a new bug?

@Etonkovidova this isn;t so much as bug, as an unsupported feature that is still "broken" in 5.0, even if the error messages have been removed. I will move it back to PM backlog, since we need to spec out the better expected behavior.

JMinor raised the priority of this task from Low to Medium.Jan 26 2016, 11:28 PM
JMinor edited projects, added iOS-app-v5.1.0-Saturn; removed iOS-app-v5-production.
JMinor renamed this task from iOS: Special pages do nothing when clicked to Special pages should open in Safari.May 9 2016, 9:14 PM
JMinor lowered the priority of this task from Medium to Lowest.

Retitled to reflect desired behavior. Basically if the app cannot support a mediawiki page it should push to the browser.