139214 - File > Open should include *.xpi

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, enhancement)

Description

[Roger]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/00200203
BuildID:    Mozilla
Mozilla 1.0 Release Candidate 1
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/00200203

When clicking File > File Open in the toolbar, the browser should also include
filtering for *.xpi files (*.html, *.htm, *.txt, *.png, etc...)!!!!

I've downloaded the jre.xpi/jre131.xpi so many times and it is somewhat
frustrating that this (considered) native extension for mozilla isn't filtered.
Or are not xpi's considered mainstream enough yet?

..just a thought.

Reproducible: Always
Steps to Reproduce:
1.Click File > File Open
2.
3.

Actual Results:  Have to sort thru all files in a folder to find an *.xpi
extension file. 

Expected Results:  Should filter *.xpi's also (ie jre131.xpi, jre.xpi, etc)

Comment 1

[Håkan Waara]

Agreed; and add "*.XUL" while you're at it -- whoever fixes this bug!

Comment 2

[Samir Gehani]

-> GUI Features

Comment 3

[Nicolas Dietrich]

*** Bug 235869 has been marked as a duplicate of this bug. ***

Comment 4

[Nicolas Dietrich]

*** Bug 196830 has been marked as a duplicate of this bug. ***

Comment 5

[Boris Zbarsky [:bzbarsky]]

See bug 196830 comment 2 and bug 196830 comment 5.

Comment 6

[timeless]

bz:
http://viper.haque.net/~timeless/blog/23/ http://viper.haque.net/~timeless/blog/24/

in short, yes i believe we should list all the extensions our plugins can
handle. as for xpi, sure, i'd say we go ahead and bury it under that list.

Comment 7

[Asa Dotzler [:asa]]

*** Bug 263303 has been marked as a duplicate of this bug. ***

Comment 8

[Asa Dotzler [:asa]]

*** Bug 222185 has been marked as a duplicate of this bug. ***

Comment 9

[Marc Bejarano]

hardware should -> All

duped bug 222185 was macintosh

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420