Closed Bug 738848 Opened 13 years ago Closed 13 years ago

FormAssistant null error when Fennec is in background

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Firefox 14

People

(Reporter: bnicholson, Assigned: bnicholson)

Details

Attachments

(1 file)

Attached patch patchSplinter Review
window.content may be null if the tab isn't active. While a page is loading, if it's put in the background, JS will give this error: 03-23 11:17:55.956 10081 10091 E GeckoConsole: [JavaScript Error: "content is null" {file: "chrome://browser/content/browser.js" line: 2934}] Rather than using content.document, I think we can use BrowserApp.selectedBrowser.contentDocument, which doesn't change if the tab is active/inactive.
Attachment #608909 - Flags: review?(mark.finkle)
Attachment #608909 - Flags: review?(mark.finkle) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 14
This wasn't marked as a blocker. Should we be working on things like this right now?
(In reply to Damon Sicore (:damons) from comment #3) > This wasn't marked as a blocker. Should we be working on things like this > right now? It was found during work on blockers. JS errors have a tendency to just cause parts of the app to stop working. Brain (and others) have periodically run out of blockers, so I was fine with this fix.
Error is no longer seen in the logs on Nightly 16.0a1 2012-06-12 and Aurora 15.0a2 2012-06-11 on HTC Desire running Android 2.2. Closing the issue as verified.
Status: RESOLVED → VERIFIED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: