Closed Bug 1051002 Opened 10 years ago Closed 10 years ago

Can't run for (let .. in window.navigator) loops, because NS_ERROR_FACTORY_NOT_REGISTERED is raised by for(let .. in window.navigator)

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1094714

People

(Reporter: kevink9876543, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Iron/31.0.1700.0 Chrome/31.0.1700.0 Safari/537.36

Steps to reproduce:

SeaMonkey 2.31 built from c-c rev 53be54f7311a / m-c rev 5e74101ce59e
new profile

Try to run a "for (let .. in window.navigator)" loop iterating over the content window's navigator object.  One way to do this is by installing NoScript latest development build from

http://noscript.net/getit#devel

setting about:config -> noscript.allowURLBarJS to true, and entering in the URL bar

javascript:try{for(let i in window.navigator){console.log(i)}}catch(e){alert(e)}


Actual results:

Produces an alert box with this error:

[Exception... "Factory not registered"  nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame :: chrome://noscript/content/JSURL.js :: <TOP_LEVEL> :: line 70"  data: no]

Running the for loop in a way that dumps the error into the Error Console instead doesn't give any additional information.

(Note that this is different from bug 1019021 in that it fails even running SeaMonkey straight from the object directory.)


Expected results:

The for loop should have run.
OS: Windows 7 → Linux
Summary: Can't run for (let .. in window.navigator) loops → Can't run for (let .. in window.navigator) loops, because NS_ERROR_FACTORY_NOT_REGISTERED occurs by (let .. in window.navigator)
Summary: Can't run for (let .. in window.navigator) loops, because NS_ERROR_FACTORY_NOT_REGISTERED occurs by (let .. in window.navigator) → Can't run for (let .. in window.navigator) loops, because NS_ERROR_FACTORY_NOT_REGISTERED occurs by for(let .. in window.navigator)
Summary: Can't run for (let .. in window.navigator) loops, because NS_ERROR_FACTORY_NOT_REGISTERED occurs by for(let .. in window.navigator) → Can't run for (let .. in window.navigator) loops, because NS_ERROR_FACTORY_NOT_REGISTERED is raised by for(let .. in window.navigator)
FYI.
I couldn't see problem of this bug in SeaMonkey 30.0b1.
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/releases/2.30b1/win32/en-US/	seamonkey-2.30b1.zip  05-Oct-2014
FYI.
"First successful seamonkey-2.31a1.en-US build in SeaMonkey trunk nigtly" seems following(linux build and mac build only).
Before it, build failure looks to haave been continuously occurred.
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2014/09/2014-09-01-00-30-05-comm-central-trunk/
"First seamonkey-2.32a1.en-US build in SeaMonkey trunk nigtly" is perhaps following(linux build and mac build only)
> http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2014/09/2014-09-11-08-37-32-comm-central-trunk/
FYI.
Tb's Bug 1057251 has bee closed as dup of Bug 1081190.
No need of SeaMonket version of Bug 1081190?
@WADA: the TB bug you referenced implies that for (let .. in window) is broken.  That worked for me when I reported this bug.
So I'd say no, this bug is not a DUP of bug 1081190.
Bookmarklet which can be used to test/reproduce:

data:text/html;base64,PGh0bWw+PGJvZHk+PHNjcmlwdD52YXIgaW5mbz0nQnJvd3NlciBJbmZvcm1hdGlvb
jo8YnI+JzsgZm9yKHZhciBwcm9wIGluIG5hdmlnYXRvcil7aWYodHlwZW9mIG5hdmlnYXRvcltwcm9wXSAhPSAn
ZnVuY3Rpb24nICYmIHR5cGVvZiBuYXZpZ2F0b3JbcHJvcF0gIT0gJ29iamVjdCcpIGluZm8rPXByb3ArJzogJytuYX
ZpZ2F0b3JbcHJvcF0rJzxicj4nfTtkb2N1bWVudC5vcGVuKCk7ZG9jdW1lbnQud3JpdGUoaW5mbyk7ZG9jdW1lb
nQuY2xvc2UoKTs8L3NjcmlwdD48L2JvZHk+PC9odG1sPg==

(from, http://forums.mozillazine.org/viewtopic.php?f=5&t=2895287)
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to kevink9876543 from comment #0)

> javascript:try{for(let i in
> window.navigator){console.log(i)}}catch(e){alert(e)}
> 
> 
> Actual results:
> 
> Produces an alert box with this error:
> 
> [Exception... "Factory not registered"  nsresult: "0x80040154
> (NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame ::
> chrome://noscript/content/JSURL.js :: <TOP_LEVEL> :: line 70"  data: no]

This looks like: https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c17
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.