177106 - localhost doesn't work in popup whitelist

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Marc Boullet]

If I enter localhost as the name of a site allowed to popup windows, it
does not work.

If I enter my IP address, it works.

Comment 1

[Marc Boullet]

--> to hyatt who seems to work on the whitelist stuff

Comment 2

[Asa Dotzler [:asa]]

This is a backend issue and not phoenix specific (I believe). Over to dveditz
for investigation. 

Comment 3

[Ken Franken]

Possibly related, the UI doesn't work for whitelisting local files, at least on
Windows. Example: file:///E:/test/test.html

Comment 4

[R.K.Aa.]

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

Comment 5

[Michiel van Leeuwen (email: mvl+moz@)]

If i go to the popupmanager, type "localhost" in the box, press add, localhost
is added to the list.
If i close the manager, reopen it, there is still a localhost entry.
(tested on seamonkey)
What doesn't work?

Comment 6

[Mark Bergman]

(In reply to comment #5)
> If i go to the popupmanager, type "localhost" in the box, press add, localhost
> is added to the list.
> If i close the manager, reopen it, there is still a localhost entry.
> (tested on seamonkey)
> What doesn't work?

When I first posted the bug, almost 18 months ago, the procedure that you
described above did not work. As I recall, the circumstances were that I was
running Cisco training scenarios on my local Linux machine, the default
popupmanager setting was "whitelist", and popups from "localhost" were being
denied. At that time, I could add my local (dynamic) IP to allow the popups, but
I could not add localhost. It is possible that I was able to add a localhost
entry to the whitelist table, but that it was not being respected. This was
always under Linux, and I never ran Mozilla or tested this issue under Windows.

In any case, I don't remember more specifics from October, 2002. With Mozilla
1.7b (build ID 2004031613) Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b)
Gecko/20040316 MultiZilla/1.6.3.0e, it seems to be working (after minimal testing).

Comment 7

[Michiel van Leeuwen (email: mvl+moz@)]

So, this is worksforme now?

Comment 8

[R.K.Aa.]

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

Comment 9

[Kim]

(In reply to comment #7)
> So, this is worksforme now?

To merely add the literal "localhost" to the list, yes that works.

To actually get popup windows from local files whitelisted, NO it does not work.
See bug 251791 which lists what I tested on my system.

-------------
(In reply to comment #0)
2002> "If I enter my IP address, it works."

In 2004, Mozilla 1.7, it did not work for me, either absolute IP address or
127.0.0.1

In any case, thank you one and all for your efforts!

Comment 10

[Michiel van Leeuwen (email: mvl+moz@)]

Then this isn't the same bug.
file:// != http://localhost

Comment 11

[Kim]

agreed, this is not the same as bug 251791

------------------

A prior suggestion was that:
     "file://filename"
should permit popups from that file.

a natural extension is:
     "file://wildcard filename expression"
permit popups from all files under a given directory (application)
without having to list umpteen individual filenames.
      example: "file://c:/program files/widget/*.html"

Comment 12

[OstGote!]

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

Comment 13

[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 14

[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 15

[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 16

[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