Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.straub-nv.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <1705808.IsNegvxEar@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Mon, 10 Dec 2012 19:36:34 +0100 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <1609195.3fhKV6gEnR@PointedEars.de> <7546793.cFEfZxNJhn@PointedEars.de> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 93 NNTP-Posting-Date: 10 Dec 2012 19:36:35 CET NNTP-Posting-Host: f836467c.newsspool3.arcor-online.net X-Trace: DXC=LbRY>ZS9Lekm7>ihJR;B_cMcF=Q^Z^V3h4Fo<]lROoRa8kFK`SE1ZM0Cjc?aa^d=nQYC>Pg X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:17658 Scott Sauyet wrote: > Thomas 'PointedEars' Lahn wrote: >> Scott Sauyet wrote: >>> Thomas 'PointedEars' Lahn wrote: >>>> Scott Sauyet wrote: >>>>> JeffG wrote: >>>>>> [ ... ] >>>>>> For some reason, the function is unable to return the style.display >>>>>> value that was set by the CSS file [ ... ] >>>>> `someElement.style` represents the collection of properties known to >>>>> the Javascript engine, which is, chiefly, the ones set by that >>>>> engine. > […] > I do understand the DOM APIs. No, evidently you do not. > I'm arguing that they are not relevant to the user's question. Which is wrong. The “style” property of element *host* objects is there *because of* the DOM APIs, not because of a script engine. > Did you really not understand that? I fully understand that and why you are wrong. > Or are you being intentionally obnoxious? I am trying to tell you that and why you are wrong, but you are not listening. > Seriously, though, if you think the name is so bad, have you organized > a CFV to create a different group, one which would focus correctly on > the specification? If not, why not? There is no need for a different newsgroup. This newsgroup has evolved into what you do not want to see: a newsgroup for discussions about ECMAScript implementations and their applications, whereas the latter naturally includes the DOM API. The newsgroup does not need to be renamed, because JavaScript still is an ECMAScript implementation (although its tagline should be updated). And it should not be renamed because then – given especially misconceptions such as you have them – it would be harder to find for the interested, and all people who have already subscribed or are peering the newsgroup would have to change their setups. > I am a working Javascript programmer. No, you are not. > I code eight or nine hours per day, almost all of that in Javascript. No, you don't. > I certainly believe there is such a thing as Javascript. Then you are a fool. > I work with it every day. An incompetent fool. I pity your customers already. > I do understand that there are distinct implementations that adhere to > varying degrees to the ECMAScript specification. Evidently you have not understood anything of what I told you. > But I am not an ECMAScript programmer. Yes, at least in a way you are (you are using ECMAScript implementations; if you script SVG you are using ECMAScript for real), but you refuse to accept it. > I am a Javascript programmer. See what I mean? > Your repeated incorrect assertions that the subject matter of my job > doesn't exist is a minor irritant. I am working as a Web application developer. That includes, but is not limited to, using ECMAScript implementations such as Mozilla JavaScript, Microsoft JScript, Google V8 JavaScript, Apple JavaScriptCore, Opera ECMAScript, and KDE JavaScript, to manipulate web browsers and web documents through implementations of DOM APIs. PointedEars -- var bugRiddenCrashPronePieceOfJunk = ( navigator.userAgent.indexOf('MSIE 5') != -1 && navigator.userAgent.indexOf('Mac') != -1 ) // Plone, register_function.js:16