Closed Bug 230418 Opened 21 years ago Closed 21 years ago

mozilla addressbook opens browser window to find.com when starting up (history sidebar?)

Categories

(SeaMonkey :: Sidebar, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 128322

People

(Reporter: wouter-mozilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020527
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020527

When I open the addressbook, mozilla suddenly started opening a browser window
to find.com every time since a few days ago. I think it has something to do with
the history sidebar, for some reason, trying to access this link:

find:datasource=history&match=AgeInDays&[...]

I found links like this in localstore.rdf:

  <RDF:Description
about="find:datasource=history&amp;match=AgeInDays&amp;method=is&amp;text=2&amp;datasource=history&amp;match=Hostname&amp;method=is&amp;text=www.merimieskirkko.fi"
                   NC:open="true" />
  <RDF:Description
about="find:datasource=history&amp;match=AgeInDays&amp;method=is&amp;text=1&amp;datasource=history&amp;match=Hostname&amp;method=is&amp;text=health.groups.yahoo.com"
                   NC:open="true" />

I guess it tries to 'resolve' the find: procedure (whatever it's supposed to
do), can't find the procedure, and then decides to append www. and .com to the url.

I don't understand why this code is executed (improperly) though. And obviously,
I don't want to be referred to "find.com" every time I open my addressbook...

Reproducible: Always

Steps to Reproduce:
1. Open addressbook
2. For some reason, a browser window is opened and after some url redirecting,
it ends up on find.com
Actual Results:  
An unwanted browser window with www.find.com in it.

Expected Results:  
Mozilla should not open a browser window when doing something that looks like
internal url procedures, even if appending 'www.' and '.com' is enabled. When
mozilla is using urls to access internal procedures, it should be no means
accidently end up going to real urls. Perhaps this even has security implications.
Wait.  1.0rc3?  This was fixed, but _way_ after that.  Possibly after 1.0 final,
even.  Please test a recent build.

*** This bug has been marked as a duplicate of 128322 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.