Path: csiph.com!weretis.net!feeder4.news.weretis.net!feeder1.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: "Christoph M. Becker" <cmbecker69@arcor.de>
Newsgroups: comp.lang.javascript
Subject: Re: JSlint complains for requestFullscreen
Date: Sat, 2 Apr 2016 18:58:24 +0200
Organization: solani.org
Lines: 31
Message-ID: <ndotmq$bjb$1@solani.org>
References: <ndndbq$1nfl$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: solani.org 1459616282 11883 eJwNyUkBwDAIBEBL4QY5ZAn+JbTzHRMnR6ibq63t+rxhpSiw152zR1WTVGOSQWtHsruYntSSEmJ4Ymj+hHUC4RBOBJXYKUx0IXo6S258d8od/g== (2 Apr 2016 16:58:02 GMT)
X-Complaints-To: abuse@news.solani.org
NNTP-Posting-Date: Sat, 2 Apr 2016 16:58:02 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
X-User-ID: eJwFwQkRwEAIBDBLx7eAnMIs/iU0CYNg0xHwuLjHdfrMXoKHI+aLEtNBneYroo0tXZuiVT8z9BEh
In-Reply-To: <ndndbq$1nfl$1@gioia.aioe.org>
Cancel-Lock: sha1:tSyDX4zt7xJE8bEQwn4S7RH3KLw=
X-NNTP-Posting-Host: eJwNytEBRDEEBMCWvMWSciLov4S7+R5XfnxhdJqvr9hD2Zi062Zo7qmIb+JfekB0Kqx3Ug1upVCrYz03jwrZWffSG6DXLrMQwsXZOSXxfmRiHbQ=
Xref: csiph.com comp.lang.javascript:30191

emf wrote:

> in my Eye Exercises I am using this borrowed full-screen function:
>
> [code]
> 
> It works fine, however JSlint complains for the last line of code:
> 
> Expected 'new' before 'wscript'.
>             wscript.SendKeys("{F11}");
> 
> Sincerely I do not understand what the problem is and what JSlint wants
> me to change -- the variable has been declared and has been assigned a
> value -- and adding new in front creates more problems and doesn't make
> sense to me. Can someone explain what the problem is and how it can be
> solved to JSlint's satisfaction?

I assume that JSLint assumes that wscript.SendKeys is a constructor
function, because SendKeys starts with a capital letter.  Therefore
JSLint complains.

> also, I am curious, why did the author chose el as a variable name?

el is most likely an abbreviation of element.

> And do the experts of this newsgroup consider the code up-to-date?

I'm don't consider me an ES expert, so I can't comment. :)

-- 
Christoph M. Becker