Closed Bug 982019 Opened 11 years ago Closed 4 years ago

Going back to a page in reader mode, fails to load the article

Categories

(Firefox for Android Graveyard :: Reader View, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox27 affected, firefox28 affected, firefox29 affected, firefox30 affected, firefox31 affected, firefox32 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox27 --- affected
firefox28 --- affected
firefox29 --- affected
firefox30 --- affected
firefox31 --- affected
firefox32 --- affected

People

(Reporter: cos_flaviu, Unassigned)

References

Details

(Keywords: regression, reproducible)

Environment: Device: Samsung Galaxy S3 (Android 4.3); Build: Nightly 30.0a1 (2014-03-10); Steps to reproduce 1. Go to mozilla.org. 2. Tap on Reader Mode icon. 3. Tap on a link. 4. Tap on Back button. Expected result: Mozilla.org should be loaded in reader mode. Actual result: The previous page(mozilla.org) is not loaded and the "Failed to load article from page" message is displayed.
Flags: needinfo?(flaviu.cos)
Last good revision: 0d50cb959c46 (2013-04-21) First bad revision: 50d25e083421 (2013-04-22) Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0d50cb959c46&tochange=50d25e083421
Flags: needinfo?(flaviu.cos)
Wonder if this has been broken for a long time? Only one bug of possible interest, but it doesn't look related now does it? Lucas? e07d7cf9649e Mark Capella — Bug 800899 - Reader Mode:Toolbar remove button is not updated, r=lucasr
Flags: needinfo?(lucasr.at.mozilla)
Keywords: reproducible
Flaviu please test this apk (fennec_kbrosnan) http://people.mozilla.org/~kbrosnan/tmp/982019/fennec-23.0a1.en-US.android-arm.apk and let us know if it is good or bad.
Flags: needinfo?(flaviu.cos)
The bug is not reproducible on the apk from the comment 3. Tested on Google Nexus 5 (Android 4.4.2) and Google Nexus 10 (Android 4.4.2).
Flags: needinfo?(flaviu.cos)
Is 27 really unaffected? The above tested APK with a possible back-out is based off of 23
Keywords: regression
It should be affected according to the regression range. The test build was 50d25e083421 with 800899 backed out.
Blocks: 800899
Flags: needinfo?(lucasr.at.mozilla)
I'm noticing Error: "TypeError: this._article is null" {file: "chrome://browser/content/aboutReader.js" line: 556}] in the logcat
I'm not able to reproduce this (at least I just tried on trunk). E.g, visit http://docs.python-guide.org/en/latest/index.html, enter Reader Mode, tap the 'fork us on Github' link, hit back. On back, I am re-entered back into Reader Mode. Tested this w/Nightly (03/12) on my Galaxy SIV (Android 4.4.2)
I can repro it in |mozilla.org| page, but not in others.
(In reply to Mark Capella [:capella] from comment #7) > I'm noticing Error: "TypeError: this._article is null" {file: > "chrome://browser/content/aboutReader.js" line: 556}] in the logcat You see this only after following the steps to reproduce this bug?
Yes ... after some then minor digging couple days ago shows failure point: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/Readability.js?mark=702-702#687 That's failing after going from http://www.mozilla.org/en-US/, to https://support.mozilla.org/en-US/kb/, then trying back to: http://www.mozilla.org/en-US/ It works on the way in, which is odd... I've got a log if it'll help
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.