Closed
Bug 1039820
Opened 10 years ago
Closed 10 years ago
"TypeError: content is null" (in tab-events.js)
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla35
People
(Reporter: zer0, Assigned: zombie)
References
Details
Attachments
(1 file)
For example, executing `test-panel` logs a lot of the following lines: System JS : ERROR resource://extensions.modules.b8c0dbc8-1668-4930-b6a9-3468ce16447f-at-jetpack.commonjs.path/framescript/tab-events.js:40 - TypeError: content is null console.log: addon-sdk: [JavaScript Error: "content is null" {file: "resource://extensions.modules.b8c0dbc8-1668-4930-b6a9-3468ce16447f-at-jetpack.commonjs.path/framescript/tab-events.js" line: 40}] However the test itself pass. Given the file's source I believe depends by the recently introduced framescript.
Assignee | ||
Comment 1•10 years ago
|
||
looked quickly into this, it's simple to fix, but i wanna investigate more to find out the cause, and since it's not breaking anything, it doesn't look like a priority, so i'll likely get to it next week.
Updated•10 years ago
|
Priority: -- → P2
Assignee | ||
Updated•10 years ago
|
Summary: "TypeError: content is null" in tests executions → "TypeError: content is null" in tests executions (in tab-events.js)
Comment 3•10 years ago
|
||
I see this constantly even when just navigating and using the browser.
Summary: "TypeError: content is null" in tests executions (in tab-events.js) → "TypeError: content is null" (in tab-events.js)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → tomica+amo
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Comment 4•10 years ago
|
||
the problem here was the usage of chromeEventListener, which :smaug advises against, as it can have a slightly different lifetime from TabChild (the implied `this` that is now used to listen for 'pageshow' events). i also took the opportunity to clean up/simplify some other code..
Attachment #8495923 -
Flags: review?(zer0)
Reporter | ||
Comment 5•10 years ago
|
||
Comment on attachment 8495923 [details] [review] Link to Github pull-request: https://github.com/mozilla/addon-sdk/pull/1657 Looks good to me! r+ with all tests passing, and possibly with the nit in the PR comment addressed.
Attachment #8495923 -
Flags: review?(zer0) → review+
Comment 6•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/5f952e1f8968a0626c7ba9ac14fdd1ef7ed89680 bug 1039820 - avoid using chromeEventHandler in framescript https://github.com/mozilla/addon-sdk/commit/974d800f18f7262d28da660c5e43775a26398516 Merge pull request #1657 from zombie/1039820-fs-chromeEventHandler bug 1039820 - avoid using chromeEventHandler in framescript, r=@ZER0
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
You need to log in
before you can comment on or make changes to this bug.
Description
•