Closed Bug 432463 Opened 18 years ago Closed 17 years ago

[Tark Extension] JavaScript Error: "tarkButton is null" {file: "chrome://tark/content/tark-Main.js" line: 139}

Categories

(addons.mozilla.org Graveyard :: Administration, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: cbook, Unassigned)

References

()

Details

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008050221 Firefox/3.0pre Steps to reproduce: -> Install the Tark Extension https://addons.mozilla.org/en-US/firefox/addon/2886 -> Start Firefox with the Tark Extension enabled --> JS Error Message in Debug output/Error Console: Call to xpconnect wrapped JSObject produced this error: * [Exception... "'[JavaScript Error: "tarkButton is null" {file: "chrome://tark/content/tark-Main.js" line: 139}]' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: stop :: line 146" data: yes]
Author has been contacted.
I got email from someone running .31 Tark on a Mac and he did not see this error. I take it this is Tark .30?
(In reply to comment #2) > I got email from someone running .31 Tark on a Mac and he did not see this > error. > > I take it this is Tark .30? > Yes its 0.30 (https://addons.mozilla.org/en-US/firefox/addon/2886 is where i got the xpi file)
I think this is a symptom of something I saw a few years ago with that specific instance. The code where this issue occurred will have a null-check in the next revision.
This should be fixed in 0.31, a version that was just submitted for review.
closing as invalid, because this is fixed in 0.31 (and no Firefox bug), thanks Rollin !
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Component: Add-ons → Administration
QA Contact: add-ons → administration
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.