Adding or removing addresses to or from the home page group throws exceptions

NEW
Unassigned

Status

7 years ago
7 years ago

People

(Reporter: rsx11m.pub, Unassigned)

Tracking

({regression, regressionwindow-wanted})

Trunk
regression, regressionwindow-wanted

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Spin-off from bug 535128. A couple of exceptions are consistently thrown when increasing or decreasing the number of browser.startup.homepage.* prefs used. On Windows, this happens when the Browser preference pane is closed and changes in the homepage group were made, increasing or decreasing the number of pages listed; on Linux, this happens already while the list is modified (in fact, the prefs are updated immediately as one types).

As far as I can tell, this has no impact on the expected functionality.

The following exception is seen when a new browser.startup.homepage.* pref has to be added which didn't exist before, only on Windows 7 though but not on Linux:

> Error: Couldn't get browser.startup.homepage.x pref: [Exception...
> "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED)
> [nsIPrefBranch2.getComplexValue]"  nsresult: "0x8000ffff
> (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
> chrome://communicator/content/utilityOverlay.js :: GetLocalizedStringPref ::
> line 194"  data: no]
> Source File: chrome://communicator/content/utilityOverlay.js
> Line: 196

Note that this exception is present in SeaMonkey 2.4.1 and later Windows builds, but not in SeaMonkey 2.3 as released. Both bug 662162 or bug 663629 were checked in during that time frame and deal with string preferences.

When the number of home pages in the group is reduced, I get this message on both platforms (and in SM 2.3 already):

> Error: this.preferences is null
> Source File: chrome://global/content/bindings/preferences.xml
> Line: 122

After reducing, then increasing the number of homepage prefs used, the following may show up in the Error Console on both platforms (this is much less reproducible though):

> Error: [Exception... "'JavaScript component does not have a method named:
> "observe"' when calling method: [nsIObserver::observe]"  nsresult:
> "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"  location: "JS
> frame :: chrome://global/content/bindings/preferences.xml ::
> set_valueFromPreferences :: line 350"  data: no]
> Source File: chrome://global/content/bindings/preferences.xml
> Line: 350

Also occasionally observed on line 333 with the same message. The last exception was seen in SM 2.0.4 as well, whereas neither of the other exceptions are thrown in the old branch.
(Reporter)

Comment 1

7 years ago
> chrome://communicator/content/utilityOverlay.js :: GetLocalizedStringPref ::

Looking a bit closer at this, bug 662162 only introduced reporting an exception if the pref is not defined, previously it was just quietly assigning a "null" and continuing. Thus, that patch simply may have exposed an issue which was around before already.
You need to log in before you can comment on or make changes to this bug.