903865 - Preferences, Managed Stored Passwords does not set Filter Passwords Only in Data Manager

Status: NEW

(SeaMonkey :: Passwords & Permissions, defect)

Description

[therube]

Edit | Preferences | Privacy & Security | Passwords -> Managed Stored Passwords, does not set filtering to 'Passwords only' in Data Manager.
 
 
> Error: document.getElementById(...).ReadConcurrentTabs is not a function
> Source File: chrome://global/content/bindings/preferences.xml
> Line: 402

> Warning: SyntaxError: yield without a value is deprecated, and illegal in ES6 (use 'yield undefined' instead)
> Source File: chrome://communicator/content/dataman/dataman.js
> Line: 349, Column: 6
> Source Code:
>      yield; 

> Warning: SyntaxError: yield without a value is deprecated, and illegal in ES6 (use 'yield undefined' instead)
> Source File: chrome://communicator/content/dataman/dataman.js
> Line: 446, Column: 6
> Source Code:
>      yield; 

> Error: TypeError: gLocSvc.domstoremgr.getUsage is not a function
> Source File: chrome://communicator/content/dataman/dataman.js

> Error: TypeError: gLocSvc.domstoremgr.getUsage is not a function
> Source File: chrome://communicator/content/dataman/dataman.js
> Line: 2344
 
 
This is a Regression.
SeaMonkey 2.19 worked correctly, 2.20 does not.

(Not sure if any, all, Error Console messages are relevant?)

Comment 1

[therube]

Oh, lets say that things aren't going to be as simple as they seem.

Observed this behavior in two existing Profiles.
(Also noted by another at mozillazine.)

With a new Profile, not able to duplicate (yet?).
In a new Profile, both SeaMonkey 2.19 & 2.20 work as expected.

Disabled all plugins in existing Profile & still 2.20 broke.
Safe mode, still broke.
Safe mode & Reset toolbars, still broke.

So not sure yet just what triggers this?

Comment 2

[rsx11m]

> Error: document.getElementById(...).ReadConcurrentTabs is not a function
> Source File: chrome://global/content/bindings/preferences.xml
> Line: 402

That's bug 868486, currently fixed on trunk only (branches pending). The "yield" errors are deprecation warnings only, thus may be still functional and that's just a heads-up that it will be changed to a real syntax error in the future.

Comment 3

[Philip Chee]

> Error: TypeError: gLocSvc.domstoremgr.getUsage is not a function
> Source File: chrome://communicator/content/dataman/dataman.js

> Error: TypeError: gLocSvc.domstoremgr.getUsage is not a function
> Source File: chrome://communicator/content/dataman/dataman.js

Does the patch in Bug 876430 (Update Dataman for changes in DOMStorage and localStorage) fix these two errors?

Comment 4

[rsx11m]

I can reproduce this only with a profile that was migrated from 2.19 to 2.20; when setting up a new profile with 2.20, it shows "All data types" for a split second before switching to "Passwords only" and adjusting the listed domains. The same applies to my 2.22a2 nightly build.

I'm also seeing the gLocSvc.domstoremgr.getUsage error only with the migrated 2.20 profile showing the problem, thus it seems to be relevant here.

BTW: I doubt that this depends on bug 868486, that's a different prefpane and should be independent from the issue seen here (it just shows up as the Browser main prefs are the default when opening the preferences from a browser window).

Comment 5

[Peter Schmidt]

Get this problem on 3 different systems after migrating from 2.19 to 2.20 .
In addition I see some like problems easy to reproduce:
From menu bar: Tools > Cookie Manager > Manage Stored Cookies = fails to set "Cookies only" for listed Domains.
Same for "Image Manager" and "Popup Manager" = fail to set "Permissions only".

And one more: Filter "Storage only" (as I know new in 2.19) results in a emty Domain list (This list is not emty under 2.19 !)

In all cases I only get this Message on the error console:
> Fehler: TypeError: gLocSvc.domstoremgr.getUsage is not a function
> Quelldatei: chrome://communicator/content/dataman/dataman.js
> Zeile: 2344