Closed
Bug 153767
Opened 24 years ago
Closed 24 years ago
After a plug-in error, following page load will not enable view source
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.2beta
People
(Reporter: wolruf, Assigned: serhunt)
References
()
Details
(Whiteboard: [PL2:NA])
Build ID: 2002062304 (trunk), Win2k.
Have been seeing this consistently (not a regression AFAIK) since Mozilla 0.8.
Steps to reproduce bug:
1. Load http://www.epita.fr/~cahagn_o/mozbug/test.pdf (make sure you have the
Acrobat plug-in, I use v.4 because Acrobat 4 is overloading the Acrobat Reader
v.5),
2. This will generate an error because test.pdf is a dummy file (contains
34534), this error is needed for next step,
3. Load on the same window (using URL bar):
http://www.epita.fr/~cahagn_o/mozbug/bug.html
4. Richt click on page and view source, you can also use menu View -> Page
Source or Ctrl-U,
5. It doesn't work, cannot view source, plus the context menu mentions a frame
whereas there's no frame on this page.
I've been seeing this with other plug-ins (WMP) and it's even worse when the
next page you try to load has some CSS because it won't load the CSS rendering
the page ugly. Fix for bug 133286 didn't solve this, copying the people for this
patch just in case it can be related.
Peter, looks like we are not updating document structure after failure on
full-page plugins. This is probably related to about:plugins not working after
full-page plugins.
Comment 2•24 years ago
|
||
What NPAPI function returns error?
Comment 3•24 years ago
|
||
av
Assignee: beppe → av
Priority: -- → P3
Target Milestone: --- → mozilla1.2beta
Comment 4•24 years ago
|
||
well, unfortunately we cannot programmatically detect this error state of
plugins, NPAPI simply does no have such func:(
from mozilla point of view every thing is fine it serves whole stream to the
plugin, and has no idea that plugin chokes on that data.
Comment 5•24 years ago
|
||
Perhaps bug 90256 may help with its synthetic document for full-page plugins?
Comment 6•24 years ago
|
||
The plug-ins triage team (av, beppe, peterl, serge and shrir) have reviewed this
issue and have made the following determination:
This is functional on the trunk, but not on the branch. This is likely a result
of the fix from 146143.
Shrir will verify the fix on the branch when 146143 is checked in.
| Reporter | ||
Comment 7•24 years ago
|
||
using build 2002071008 on Win2k (trunk), I confirm fix for bug 146143 is
excellent: I'm not experiencing issues anymore with this particular testcase and
the pages with CSS where I had some errors previously after having loaded PDF or
WMP.
Updated•24 years ago
|
Whiteboard: [PL2:NA]
Marking Fixed based on the reporter's comments.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•