Closed
Bug 87045
Opened 24 years ago
Closed 19 years ago
Getting exception in general.xml pressing View when looking at plugin documents (pdf, etc)
Categories
(SeaMonkey :: UI Design, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
mozilla1.2alpha
People
(Reporter: bugzilla, Assigned: hewitt)
References
()
Details
Attachments
(2 obsolete files)
If you go to: ftp://ftp.iambic.com/pilot/actionnames/anmanual.pdf and the try to use the View menuitem you get: Error: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://global/content/bindings/general.xml#browser.markupDocumentViewer (getter) :: onget :: line 0" data: no] Source File: chrome://global/content/bindings/general.xml#browser.markupDocumentViewer (getter) Line: 0
Reporter | ||
Updated•24 years ago
|
Summary: Getting exception in general.xml pressing View when looking at PDF files → Getting exception in general.xml pressing View when looking at plugin documents (pdf, etc)
Comment 2•24 years ago
|
||
BTW, when I closed the window after viewing the following URL: ftp://ftp.iambic.com/pilot/actionnames/anmanual.pdf I got a crash! Talkback ID: TB32005431Q adding crash keyword and upping severity to major. Jake
Severity: normal → major
Keywords: crash
nav triage team: Marking p2, mozilla0.9.3, nsBranch, and nsbeta1+
With fix for 80105, this no longer crashes. View menu still doesn't appear; it's really strange because when you mouse over the view menu but don't click it, it's drawn depressed as if you clicked on it. Weird. Anyway, I think this should be pushed out to mozilla1.0. Removing crash and nsBranch keywords, setting target milestone to mozilla1.0
Comment 7•23 years ago
|
||
this is a bad breakage of functionality. If we're shipping Netscape 6.1 with this, we realy shd fix the next time around. Moving up to mozilla0.9.5.
Target Milestone: mozilla1.0 → mozilla0.9.5
Took some time to look into this today. nsMenuFrame::OnCreate() exists with PR_FALSE here http://lxr.mozilla.org/seamonkey/source/layout/xul/base/src/nsMenuFrame.cpp#1592 The reason this happens is because status = nsEventStatus_eConsumeNoDefault, and the reason for that is the exception noted in this bug. My current guess is that the browserContentListener is the one being asked to QI to something it can't.
Comment 9•23 years ago
|
||
Mass-moving lower-priority 0.9.5 bugs off to 0.9.6 to make way for remaining 0.9.4/eMojo bugs, and MachV planning, performance and feature work. If you disagree with any of these targets, please let me know.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Comment 10•23 years ago
|
||
Ok, found the problem. In viewZoomOverlay.js, the calls to getMarkupDocumentViewer() are causing the exceptions. I've got a patch for that. Now the view menu shows up; however, a bunch of other view menu items cause js errors because we have no document. Sigh.
Status: NEW → ASSIGNED
Comment 11•23 years ago
|
||
Attachment #54237 -
Attachment is obsolete: true
Comment 13•23 years ago
|
||
Attachment #55250 -
Attachment is obsolete: true
Comment 15•23 years ago
|
||
Won't get time to look at this for mozilla0.9.7, moving to mozilla0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Comment 16•23 years ago
|
||
->hewitt
Assignee: pchen → hewitt
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.8 → ---
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
Comment 17•23 years ago
|
||
nsbeta1- per Nav triage team, if this crashes in recent builds, please renominate.
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.0 → mozilla1.2
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
Comment 18•19 years ago
|
||
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050604 using http://www.adobe.com/epaper/spotlights/comicsone/pdfs/Comics_One.pdf (ftp://ftp.iambic.com/pilot/actionnames/anmanual.pdf no longer exists)
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•