Closed
Bug 44692
Opened 25 years ago
Closed 24 years ago
Default plugin doesn't do anything if no mimetype specified in EMBED tag
Categories
(Core Graveyard :: Plug-ins, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: shrir, Assigned: serhunt)
References
()
Details
(Whiteboard: [nsbeta3+][HAVE FIX])
Attachments
(1 file)
1.37 KB,
patch
|
Details | Diff | Splinter Review |
Build:2000070608
I see this problem on windows build. Right now bug 43500 is not fixed (default
plugin is not added to plugins folder automatically). So you will have to wither
use the mozilla build or manually put the npnul32.dll file in the plugins
folder to recreate this problem.
Steps:
1. Go to the above mentioned url.
2. You should see a square box on the right side with a puzzle symbol and text
saying 'Click here to get the plugin'.
3. Clicking with the mouse on the icon does not do anything.
Expected: Idwally, I should be sent to the Netscape plugin download page like in
4.x browser.
Reporter | ||
Comment 1•25 years ago
|
||
Nominating this for nsbeta2 since this is major and is required to be working
for beta2.
Keywords: nsbeta2
The mime type is not specified in the source of the embed tag. That's why the
default plugin is doing nothing. The mechanism for retrieving the mime type by
extension is still to be implemented (43556). Adding dependency.
Status: NEW → ASSIGNED
Depends on: 43556
*** Bug 42696 has been marked as a duplicate of this bug. ***
Changing summary.
Summary: Clicking on 'Get Plugin' icon does not do anything → Default plugin doesn't do anything if no mimetype specified in EMBED tag
Comment 6•25 years ago
|
||
So for content providers, the workaround for this bug is to explicitly specify
the MIME type in the EMBED tag. We want to be backwardly compatible with Nav4
behavior on content, so we would still like to fix this bug, but the fact that a
workaround exists lowers the priority on this bug if we run out of time.
Reporter | ||
Comment 7•24 years ago
|
||
nominating for nsbeta3. Quicktime site is a widely used site and we are not sure
when the content providers will be making this change.
Comment 9•24 years ago
|
||
Approving for beta3: looks like the dependendent bug 43556, which is also
beta3+, should fix this?
Whiteboard: [nsbeta3+]
Assignee | ||
Comment 10•24 years ago
|
||
With couple of lines of code -- yes, it should.
Comment 11•24 years ago
|
||
I don't understand the dependency. How is the operating system going to know
what the correct mimetype is if the user hasn't already downloaded the plugin?
Wouldn't it make more sense to ask http://cgi.netscape.com/cgi-bin/plug-
in_finder.cgi to guess the mimetype based on the extension?
(on Windows, Mozilla currently goes to
http://cgi.netscape.com/cgi-bin/plug-in_finder.cgi?video/quicktime when given a
mimetype of quicktime and when there is no "video/quicktime" entry in
HKEY_CURRENT_USER\Software\Netscape\Netscape Navigator\Default Plugin)
Assignee | ||
Comment 12•24 years ago
|
||
My guess is we are supposed to use HKEY_CLASSES_ROOT where tons of mime types
are associated with file extensions even before a given plugin is installed.
This is a good question to ask mscott (see 43556).
Assignee | ||
Comment 13•24 years ago
|
||
I've got a fix. Should we pump the priority up to get it in? Erick?
Whiteboard: [nsbeta3+] → [nsbeta3+]{FIX IN HAND]
Whiteboard: [nsbeta3+]{FIX IN HAND] → [nsbeta3+][HAVE FIX]
Comment 14•24 years ago
|
||
Yes. This is a P1 because Apple is a high profile partner and QuickTime is a
high profile plug-in. This is also high profile backward compatibility. Setting
priority to P1. Please check in fix as soon as you get any needed reviews.
Priority: P3 → P1
Assignee | ||
Comment 15•24 years ago
|
||
Assignee | ||
Comment 16•24 years ago
|
||
The fix is in. Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 17•24 years ago
|
||
This is fixed on windows. Marking verified (build 2000092212m18)
Status: RESOLVED → VERIFIED
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•