Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #19985

Re: Scroll position detection

Path csiph.com!usenet.pasdenom.info!gegeweb.org!newsfeed.kamp.net!newsfeed.kamp.net!87.79.20.101.MISMATCH!newsreader4.netcologne.de!news.netcologne.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Content-Type text/plain; charset="UTF-8"
Message-ID <1678891.pDxAfIlnAs@PointedEars.de> (permalink)
From Thomas 'PointedEars' Lahn <PointedEars@web.de>
Reply-To Thomas 'PointedEars' Lahn <usenet@PointedEars.de>
Organization PointedEars Software (PES)
Date Mon, 27 May 2013 21:10:10 +0200
User-Agent KNode/4.10.2
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+&.<b';Md8`dH6iqhT)6C^.Px|[=M@7=Ik[_w<%n1Up"LPQNu2m8|L!/3iby{-]A+#YE}Kl{Cw$\U!kD%K}\2jz"QQP6Uqr],./"?;=4v
Face iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXTxa4RFk5dUWANED8PFEfy7+MGBiW+n3ZNF/QuAAACaElEQVQ4jVXUwVOcMBQG8Dc7Rc4PUntdWV2uxjDpGaGeozOp1woar4jd5t/v9wLstMwsA/ntlxdCAgUc1hjTc9/JCZfGoo3wG3HdmdAWrIJRHe7GM/TmpY5VFefuVcAkkPbLIaN8rmPmjloyZxgyR3GuJ4K0AGtJ2htz8o7yqikm759fldQXaMpbDzjKAG+8v+AugVTOPO5DOjLvGtUYQwh0CPjnVMyGd+8/GfUB5nLKJDD2aLDh5HYyMDJGDwQIo2ZmZcKbowNmAdB/AzyFhrmF2MHRb0QJJfaAnwGB6orZhoykLzJtGwF/xpYxI1dswomiUj3gTuAIqCn/4C7cULwGNBtwMTk3Y4LfKB5YUaOKBKYtpplm7u0vip8tU1NWWyI/7XdcSuIDoMt6rVHMWT0DbjHPGqDqZVSa6zleLcUTcIKLoMv3ueJluALtAo9B302zPPlrtiVScRdCjXvVh3e3JpYa/jjkuC9N+LrBMlz/eAN4eQijX2EdLo6c5tGGHwLyHFtXk89dDGHwCVhG9T0S/j55AhRZgkMCmUQXJ49TnS1wnQDvw0eAh9ICeMmEFbCnPMFzjAvsWoEWEFdYEx+S0MoUZ1gT1wId8+AF3Bl2OoEu906AUHx5VLw/gXYg/x84loOah/2UYNrgiwSwGO7RfUzVBbx/kgpckumGOi6QirtD6gkLTitbnxNol47S2jVc2vsN5kPqaAHT8uUdAJM4v/DanjYOwmUjWznGfwB7sGtAtor5BgofDuzaRj4kSQAqDakTsKORa3Q3xKi3gE1fhl71KRMqrdZ2AWNNg/YOhQyrVBnb+i+nEg4bsDA+egAAAABJRU5ErkJggg==
Subject Re: Scroll position detection
Newsgroups comp.lang.javascript
References <knq2it$m8o$1@news.albasani.net> <XnsA1CB865D2BD6Aeejj99@194.109.133.133> <knum6d$7iu$1@speranza.aioe.org> <10408762.JzxCSuINyj@PointedEars.de> <knvjri$jvv$1@speranza.aioe.org> <knvk20$sdf$1@dont-email.me> <knvl83$nvp$1@speranza.aioe.org> <28567346.elAEKrzd9Y@PointedEars.de> <knvsaa$dmv$1@speranza.aioe.org> <1886046.z6t1GHbE6s@PointedEars.de> <ko00lg$r85$1@speranza.aioe.org> <1614253.6SbFCPW3aX@PointedEars.de> <ko08c2$i11$1@speranza.aioe.org>
MIME-Version 1.0
Lines 55
NNTP-Posting-Date 27 May 2013 21:10:21 CEST
NNTP-Posting-Host 2203f92b.newsspool4.arcor-online.net
X-Trace DXC=bYg9N^0=gXA^B]`=U:WelB4IUK<Cl32<A4Fo<]lROoRA8kF<OcfhCOKEUNnbbFTL3BDZm8W4\YJNLb@mF9jNikdEIQbgJMhLo0GUBdh7\K7=nH
X-Complaints-To usenet-abuse@arcor.de
Xref csiph.com comp.lang.javascript:19985

Show key headers only | View raw


Joao Rodrigues wrote:

> On 27/05/2013 14:41, Thomas 'PointedEars' Lahn wrote:
>> Joao Rodrigues wrote:
>>> On 27/05/2013 12:27, Thomas 'PointedEars' Lahn wrote:
>>>> you claimed something that I have proven wrong.
>>> You have proven?! You have only spotted that was a W3C's Working Draft;
>>> ie, a Recommendation to-be in some time in the future. Just that!
>>
>> A Working Draft ist _not_ “a Recommendation to-be some time in the
>> future”. It is something that *might become* a Recommendation some time
>> in the future.  Not only the W3C Process Document, that I cited, but also
>> the paragraph that I quoted from the very document that you cited makes
>> that *very* clear to anyone who can read.
> 
> The W3C Editors' Draft has just been updated (27 May 2013):
> <http://dev.w3.org/csswg/cssom-view/>
> 
> Note that the pageYOffset attribute (which actually returns the same
> value returned by the scrollY attribute) is just one item among many
> others of that document. AFAIC pageYOffset hasn't changed since the
> latest version of the Working Draft.

An Editor's Draft has even less significance than a Working Draft.  A 
Recommendation has the support of the W3C Membership, which is why it is 
reasonably called a “Web standard”.  A Working Draft usually (but not 
always) has the support of all people of the Working Group (and so, it can 
be assumed, by the companies they work for, unless they are independent 
invited experts).  An Editor's Draft does not have even that.

> Nowadays, pageYOffset is widely supported by *all* major web browsers
> (IE9+, FF3+, Safari 4+, Chrome 4+, Opera 10+) since the Working Draft
> was produced by the W3C's CSS Working Group (people from Microsoft,
> Google, Mozilla, Opera, Apple, Adobe, W3C Staff, HP, Intel, etc., even
> from jQuery Foundation - sorry to let you know that.)
> <http://www.w3.org/Style/CSS/members>

Do you really not realize how embarrassing your continuing unfounded, stupid 
megalomania is for you?  I have been doing professional Web development for 
13 years now, Web development in general even longer, and I certainly do not 
need to be lectured – by you of all people – about browser support or the 
W3C.
 
> Therefore, going back to the OP's code, I cannot see any reason to not
> test for window.pageYOffset before testing for the MSIE proprietary
> scrollTop.

The thing that you apparently are unable to understand is that *both* 
properties are nothing but proprietary as of now.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Scroll position detection Tuxedo <tuxedo@mailinator.com> - 2013-05-25 12:08 +0200
  Re: Scroll position detection "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-05-25 13:12 +0200
    Re: Scroll position detection Tuxedo <tuxedo@mailinator.com> - 2013-05-25 16:02 +0200
    Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 01:07 -0300
      Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 11:48 +0200
        Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 09:33 -0300
          Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 14:39 +0200
            Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 11:33 -0300
              Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 16:42 +0200
          Re: Scroll position detection Denis McMahon <denismfmcmahon@gmail.com> - 2013-05-27 12:37 +0000
            Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 09:57 -0300
              Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 16:45 +0200
                Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 11:58 -0300
                Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 17:27 +0200
                Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 13:12 -0300
                Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 19:41 +0200
                Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 15:24 -0300
                Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-27 21:10 +0200
                Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 18:35 -0300
                Re: Scroll position detection Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-05-28 00:00 +0200
                Re: Scroll position detection Stefan Weiss <krewecherl@gmail.com> - 2013-05-28 02:30 +0200
      Re: Scroll position detection Denis McMahon <denismfmcmahon@gmail.com> - 2013-05-27 10:16 +0000
        Re: Scroll position detection Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2013-05-27 09:45 -0300
          Re: Scroll position detection Denis McMahon <denismfmcmahon@gmail.com> - 2013-05-27 21:24 +0000

csiph-web