Closed
Bug 138700
Opened 23 years ago
Closed 22 years ago
Javascript not reading browser.startup.homepage
Categories
(SeaMonkey :: Preferences, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: davidstl, Assigned: bugs)
Details
Attachments
(2 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+)
Gecko/20020419
BuildID: 2002041903
I tried to open a file saved on my hard drive that would read what my startup
homepage is. This was the code:
<script>
netscape.security.PrivilegeManager.enablePrivilege("UniversalPreferencesRead");
var homepage = navigator.preference("browser.startup.homepage");
alert(homepage);
</script>
The alert said "chrome://navigator-region/locale/region.properties". But my
startup homepage is the default http://www.mozilla.org/start
Reproducible: Always
Steps to Reproduce:
1. Save the file I will attach to your hard drive
2. Browse to it and open
3. Compare result to what your startup homepage really is
Actual Results: Says chrome://navigator-region/locale/region.properties
Expected Results: Should display my homepage.
I'll upload a test file.
Reporter | ||
Comment 1•23 years ago
|
||
Reporter | ||
Comment 2•23 years ago
|
||
Comment 3•23 years ago
|
||
-> Preferences, this is not a JavaScript engine problem.
Assignee: rogerl → ben
Component: JavaScript Engine → Preferences
QA Contact: pschwartau → sairuh
Comment 4•22 years ago
|
||
WFM with 2002112607/trunk/win2k (script pops up alert with my homepage location)
reporter (David): can you reproduce this bug with a recent build of mozilla (for
example, 1.2)? if so, please comment again with details. if not, please resolve
this bug as WORKSFORME. thanks.
Comment 5•22 years ago
|
||
no response from reporter for >30 days. resolving WORKSFORME.
reporter: if you can reproduce this with a recent build of mozilla, please
reopen this bug and give details. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•