Closed Bug 272447 Opened 20 years ago Closed 19 years ago

When I click on pagebuilder in Geocities it prompts a missing plugin download. This plugin has been installed or so it says, and pagebuilder still doesnt load.

Categories

(Toolkit Graveyard :: Plugin Finder Service, defect)

x86
Windows ME
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: joeye423, Assigned: doronr)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

I build several websites with the geocities service. When I log into my account
and click the Pagebuilder icon, Firefox requires a java plugin. Firefox searches
for this plugin and prompts to install. I install the plugin to no avail. 

Reproducible: Always
Steps to Reproduce:
1.Log into geocities. Build a free site. 
2.Click on Pagebuilder.
3.It takes you to another page and prompts for a java plugin download.

Actual Results:  
The process starts all over again.

Expected Results:  
Pagebuilder icon should have came up and loaded the pagebuilder program. It
works flawlessly through Internet Explorer.
I get the same thing under MacOS 10.2.8 on the url
http://patimg2.uspto.gov/.piw?docid=US006360380&PageNum=1&IDKey=4D8CC0F73CD0&HomeUrl=http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2%2526Sect2=HITOFF%2526p=1%2526u=/netahtml/search-adv.htm%2526r=3%2526f=G%2526l=50%2526d=ptxt%2526S1=jillette%2526OS=jillette%2526RS=jillette
Not quite the same thing, as this is the QuickTime plugin (I know it's not the
Quicktime plugin for Windows users; some plugins are silly that way.)

IMHO, the correct behavior would be to detect 'is the plugin installed?'  If it
is, and it won't handle the attachment, flag an error regarding the content,
unless there's an alternate (and not installed) plugin.

If said logic is already in place, there's a bug in the plugin detection code.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Firefox → Toolkit
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.