Closed Bug 529202 Opened 16 years ago Closed 16 years ago

JavaScript exception when clicking root menus of "Write:" window while composing/editing a message

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fehe, Unassigned)

References

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091116 Shredder/3.0.1pre When in message "Write" mode (i.e. composing a message or viewing/editing a draft), if any menu of the "Write:" (compose) window is clicked, the following JavaScript exception is generated: Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no] Regression window: Fine: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6pre) Gecko/20091111 Shredder/3.0pre http://hg.mozilla.org/releases/mozilla-1.9.1/rev/72004f4e186d Broken: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091112 Shredder/3.0pre http://hg.mozilla.org/releases/mozilla-1.9.1/rev/57f71400f4cf Regression was first reported and fixed in Bug 476422, but has since regressed. Reproducible: Always Steps to Reproduce: 1. Click to compose a new message (or open a draft message) 2. Click any menu (i.e. "File", "Edit", etc.) of that "Write:" (compose) window 3. Observe the exception in Error Console
Version: unspecified → Trunk
Keywords: regression
This hasn't actually "regressed". Whilst we're going through the release phase we've locked the nightly builds to building with gecko 1.9.1.5. Bug 476422 got checked in after gecko 1.9.1.5 was released so as soon as we've unlocked nightlies, we'll pick up the fix again.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.