191382 - Cannot set home page through preferences dialog

Status: RESOLVED WORKSFORME

(SeaMonkey :: Preferences, defect)

Description

[Dhruva Reddy]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 MultiZilla/v1.1.22
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 MultiZilla/v1.1.22

I cannot set the home page in my preferences dialog.  I enter the desired value,
click "OK" to commit, and it reverts to the previous value (blank).

Reproducible: Always

Steps to Reproduce:
1. Bring up preferences dialog.
2. Switch to Navigator pane.
3. Enter URL.
4. Click "OK".

Actual Results:  
Home page is blank.  That is, if I bring up the preferences dialog again, the
value for the home page is again blank.

Expected Results:  
It should have saved the URL that I specified.

This also happens if I try to specify a local HTML file via the file chooser.

Comment 1

[Dhruva Reddy]

I can set the home page by editing "prefs.js", but the value to which I set it
still does not show up in the preferences dialog.

Comment 2

[Dhruva Reddy]

I also cannot change (through the preferences dialog) whether Mozilla starts
with a blank page or the home page.

Comment 3

[R.K.Aa.]

Might indicates a some syntax error in your preferences file, at some earlyer
line than where the homepage is described.

If you start mozilla from commandline - do you see any errors list to stdout?

Do you see any error in JS console?
(Clear it before starting to test, in case there are other errors there.
You access the console from Tools->Web Development->Javascript Console)

Comment 4

[Dhruva Reddy]

I get the following error in the JavaScript window when I enter the URL and the
field loses focus.

Error: navigatorData has no properties
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 163

Comment 5

[Dhruva Reddy]

I do not see anything on the command line.

Comment 6

[R.K.Aa.]

Do other changes you make to prefs.js take place as expected?

Comment 7

[R.K.Aa.]

forgot: if you edit it manually, Mozilla must not be running at the time, or
changes are overwritten.

Can you also try create a new profile and tell if the same bug happens there.

Comment 8

[R.K.Aa.]

.

Comment 9

[Dhruva Reddy]

I tried editing prefs.js for the memory cache (about the fifth line down), and
it takes as expected.

And yes, I am aware that prefs.js cannot be edited while Mozilla is running, thanks.

Comment 10

[Dhruva Reddy]

Oh dear, I can't seem to start Mozilla with a profile other than the default.

I just tried creating a new profile using the profile manager (starting this on
the command line:

    mozilla -profilemanager

When I start it up, the profile manager comes up, I select my new profile, and
it just exits.  Again, nothing on the command line.

Comment 11

[Dhruva Reddy]

I have opened bug #191872 wrt (see my last comment).

Comment 12

[R.K.Aa.]

I wonder if Multizilla is breaking your profile. Can you try uninstall it?

Comment 13

[earthsound]

Mozilla 1.3b: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b)
Gecko/20030210; Window XP, SP1

Someone should mark OS:All, as I see this in XP, as well.

I do not use Multizilla, but I have just recently noticed this. Did not ever see
it in 1.3a or below. A few things about this bug:

1) You can go to Prefs and enter a value for the Home Page Location, click on
any other menu/sub-menu and then return to the Navigator & the Home Page
Location will be blanked out. 

2) Although the pref to autocomplete URLs inline as you type is checked (and
before this bug appeared, it worked properly in previeous moz versions), as I'm
typing a URL into the Home Page Location pref textbox, it does not autocomplete.

3) For every keypress in the Home Page Location text box, I get this error in
the js console:

Error: navigatorData has no properties
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 163

4) Just bringing up the Preferences give me this error in JS Console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getComplexValue]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://communicator/content/pref/pref-navigator.js :: getDefaultPage :: line
107"  data: no]

I will try moz w/ a new profile to see if that "fixes" anything...

Comment 14

[earthsound]

I cannot open mozilla w/ any profile other than default, so I will not be able
to see if another profile "fixes" this until I'm able to use another profile. ;)
Will add my comments to bug #191872...

Comment 15

[earthsound]

Mozilla 1.4a, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a)
Gecko/20030401, Windows XP build 2600.xpsp1.020828-1920

Maybe this will help some. I took off 1.3 final and installed 1.4a, and the
first thing I noticed was that Control+T brought up a new tab that opened
google.com (although previously the new tab had always been blank). I try to set
google.com as my default home page, but after clicking OK in the prefs and
bringing the prefs back up, the default home page is blanked out again. I get
the following JavaScript Console errors while 1)opening preferences 2)typing
http://www.google.com into my default home page text box & 3) clicking OK:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIPrefBranch.getComplexValue]"  nsresult:
"0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame ::
chrome://communicator/content/pref/pref-navigator.js :: getDefaultPage :: line
107"  data: no]

Warning: reference to undefined property gData.navigatorData
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 161

Error: navigatorData has no properties
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 163

Additionally, these prefs are found in about:config:

browser.startup.homepage = http://www.google.com
browser.startup.homepage.count = 1
browser.startup.homepage_override.1 = true
browser.startup.page = 1

Comment 16

[earthsound]

an additional observation:

If I change "When Navigator starts up, display" to Blank page, click OK, then
reopen Prefs, it has been reset to Home page (which remains blank in the
Location: text field).

When I Ctrl+T to open a new tab, it always has google (which I set as home page
location) even if I select Blank page for what Navigator should start up with. :(

I also see this in prefs when opening prefs & clicking the Blank page radio button:

Warning: redeclaration of var i
Source File: 
Line: 10, Column: 21
Source Code:
            for (var i = 0; i < children.length; ++i) {

Comment 17

[earthsound]

update: I was able to get around bug 191872 by utilizing Tools>Switch Profile
(see bug 191872 comment 10).

In the newly created profile, I am still seeing this bug. :( This error appears
in JS Console when opening Edit>Preferences:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getComplexValue]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://communicator/content/pref/pref-navigator.js :: getDefaultPage :: line
107"  data: no]

The following warning appears under the following circumstances:

1) After opening Edit>Preferences when selecting any of the radio buttons under
Preferences>Navigator>"When Navigator starts up, display", no matter which radio
button is initially selected...but after clicking one of the buttons once, you
have to meet criteria in 2) to see it again...i.e. multiple clicks on the radio
buttons do not produce additional, duplicate warnings
2) After opening Edit>Preferences and Alt+Tab-bing to another mozilla window and
back (or just using the mouse to do so...i.e. clicking on the desktop to put the
Prefs window out of focus and returning focus back to the Prefs window):

Warning: redeclaration of var i
Source File: 
Line: 10, Column: 21
Source Code:
            for (var i = 0; i < children.length; ++i) {

the above warning does *not* appear if the focus in the Prefs windows is sitting
on anything but the radio buttons, i.e. if the focus is in the Navigator>Home
Page>Location text box, switching focus to something else and back to the Prefs
window does not produce the above warning.

Clicking on any Category in Prefs window and then clicking back onto the
Navigator category results in this error:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getComplexValue]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://communicator/content/pref/pref-navigator.js :: getDefaultPage :: line
107"  data: no]

For each keystroke in Prefs>Navigator>Home Page>Location text box, the following
set of error/warnings appear (in First>Last order):

***
Warning: reference to undefined property gData.navigatorData
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 161

Warning: reference to undefined property gData.navigatorData
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 161

Error: navigatorData has no properties
Source File: chrome://communicator/content/pref/pref-navigator.js
Line: 163
***

Comment 18

[HJ]

I wonder *if* this still is a valid bug report. Reporter, do you still have the
same problem?

Anyway, removing [multizilla] from the summary, because this is/was not a
MultiZilla bug, but a Mozilla bug, just look a the errors.

Oh and guys, please CC me if you think that this has anything to do with
MultiZilla, thank you.

P.s. you can always disable MultiZilla, or any other extension, with
QPrefs/Extension Management/ Simply uncheck the extension that you like to
disable. Note that you can only re-enable MultiZilla with the following chrome
URL: chrome://multiviews/content/reEnableMultiZilla.xul

Comment 19

[Dhruva Reddy]

I no longer have access to the version of Mozilla against which I reported this
bug, nor do I use Multizilla.  My current version is:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5

I just verified that I cannot reproduce the behavior that I reported with this
version.

Comment 20

[Andrew Schultz]

resolving WORKSFORME based on previous comment