Closed Bug 1238844 Opened 8 years ago Closed 8 years ago

JavaScript error: chrome://browser/content/tab-content.js, line 619: TypeError: content is null

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 46
Tracking Status
firefox46 --- fixed

People

(Reporter: xidorn, Assigned: xidorn)

Details

Attachments

(1 file)

This error is reported during fullscreen-api-race test, and could happen if user close a tab in fullscreen.
Comment on attachment 8706742 [details]
MozReview Request: Bug 1238844 - Do not call window utils if content has been null. r?dao

I'd prefer null-checking _windowUtils (and _windowUtils returning null instead of throwing, obviously).
Attachment #8706742 - Flags: review?(dao)
Comment on attachment 8706742 [details]
MozReview Request: Bug 1238844 - Do not call window utils if content has been null. r?dao

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/30489/diff/1-2/
Attachment #8706742 - Flags: review?(dao)
Attachment #8706742 - Flags: review?(dao) → review+
Assignee: nobody → quanxunzhen
https://hg.mozilla.org/mozilla-central/rev/e29a782604ac
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 46
[bugday-20160323]

Status: RESOLVED,FIXED -> UNVERIFIED

Comments:
STR: Not clear.
Developer specific testing

Component: 
Name			Firefox
Version			46.0b9
Build ID		20160322075646
Update Channel          beta
User Agent		Mozilla/5.0 (Windows NT 6.1; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
OS			Windows 7 SP1 x86_64

Expected Results: 
Developer specific testing

Actual Results: 
As expected
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: