Closed
Bug 37165
Opened 25 years ago
Closed 24 years ago
Unreconized protocal in embed/object src attribute breaks plug-in support code
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rusty.lynch, Assigned: rusty.lynch)
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
If any html page uses an embed/object tag with the URL for the src/data
attribute that has an unregistered protocol handler, the plug-in support
code in the nsObjectFrame dies ungracefully. The end result is that none
of the plug-in's methods are ever called.
This becomes evident when you try to use any plug-in that uses it's own protocol
streaming. Typically, these plug-ins will directly look up 'src' (or 'data')
and then stream the data internal to the plug-in.
For example:
<EMBED type="audio/x-pn-realaudio-plugin"
SRC="rtsp://www.some.server.com/g2video.rm"
NOLOGO=true BACKGROUNDCOLOR=white
MAINTAINASPECT=false WIDTH=200 HEIGHT=200
CENTER=true PREFETCH=true NOJAVA=true
AUTOSTART=true CONTROLS=ImageWindow
CONSOLE=display NUMLOOP=1>
In this case, Mozilla doesn't know the 'rtsp' protocol and returns
failure from NP_NewURI. But since the return value is never checked,
the code continues as if everything was ok untill someone chocks on
the null nsURI.
What should happen, is that the plug-in should be treated as if no
'src'/'data' attribute was set, and let the plug-in code decide what
to do.
Assignee | ||
Comment 1•25 years ago
|
||
Updated•25 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 2•24 years ago
|
||
I applied the patch.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•