Closed Bug 277921 Opened 20 years ago Closed 20 years ago

Clicking a plugin file link downloads it instead of loading inline.

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 273785
Milestone:
mozilla1.8beta1

People

(Reporter: camino, Unassigned)

References

(
URL
)

Details

(Keywords: regression) 

Steps:
1) Make sure you do a fresh launch of Camino.
2) When opening this url the .mov file is downloaded instead of shown inline.
http://movies.apple.com/movies/wb/batman_begins/batman_begins-tlr_320.mov
3) When going to a webpage that contains a .mov file will act normal.
http://www.apple.com/trailers/wb/batman_begins/trailer/medium.html
4) When trying again to click on the direct .mov link the movie will load inline.
This bug first appeared in the 20041203 NB, the 20041202 NB works as it should.
OK well, this got fixed by trashing the plugin registry file. What shall I do.
Hm Ok this issue stretches further then I expected.

The problem is will all plugin content. It seems as if Camino isn't aware it can
open plugin related files itself and instead downloads them. This all gets fixed
as soon as one of the plugin files is loaded within a webpage.

This is a Major issue.
Severity: major → blocker
Target Milestone: --- → Camino0.9
Summary: Clicking .mov link downloads movie instead of loading inline. → Clicking a plugin file link downloads it instead of loading inline.
I've seen this before, though I didn't know that it happened no matter what
before viewing plugins inline!
Upgrading to Core as FF has the exact same issue.
Product: Camino → Core
Target Milestone: Camino0.9 → mozilla1.8beta
Version: unspecified → Trunk
Assignee: pinkerton → nobody
Flags: blocking1.8a6?
QA Contact: plugins
If it's a core thing, then would this be a dupe/related to FF bug 273785?
1.8a6 is already finished up.
Flags: blocking1.8a6? → blocking1.8a6-
Flags: blocking1.8b?
(In reply to comment #7)
> If it's a core thing, then would this be a dupe/related to FF bug 273785?

Looks like a dup, but 273785 contains no details. I guess it's best to keep this
one live.


From what I can understand, firefox fails to load the plugins information on
startup. Result

 a) This bug; since firefox doesn't have any information on plugins, it treats
the .pdf, .swf, etc. files as ordinary downloadable files

 b) Bug 273785; empty plugins dialog

If you go to about:plugins, firefox will load the info and will correctly deal
with the files listed above.
I've looked at CVS changes during the regression period, and can see only 2
suspicious changes: some changes to nsStandardUrl that may have changed that way
that URL comparisons work, and some packaging changes.
*** Bug 278452 has been marked as a duplicate of this bug. ***
does this happen on win32 or linux, or just mac?
hard to say as the other bug lacks details, but assuming this is indeed a dupe
of bug 273785, then it's win32 and linux as well as mac.
Flags: blocking1.8b?
Flags: blocking1.8b+
Flags: blocking1.8a6-
Keywords: regression
Depends on: 273785
*** Bug 281893 has been marked as a duplicate of this bug. ***
This is really just a dup of 273785.  There's no separate issue.

*** This bug has been marked as a duplicate of 273785 ***
Status: NEW → RESOLVED
Closed: 20 years ago
No longer depends on: 273785
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.