Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #25290
| Newsgroups | comp.lang.javascript |
|---|---|
| Subject | Re: Element visible |
| From | "Evertjan." <exxjxw.hannivoort@inter.nl.net> |
| References | (5 earlier) <XnsA3665E3F5E33Feejj99@194.109.133.133> <lplgam$fdo$1@dont-email.me> <xNqdncwLDYSUGSPOnZ2dnUVZ_judnZ2d@westnet.com.au> <XnsA36693CBE765Beejj99@194.109.133.133> <f5f186c8-45a5-440a-a206-7bf6280af7dc@googlegroups.com> |
| Date | 2014-07-11 00:23 +0200 |
| Message-ID | <XnsA3673E7A8C65eejj99@194.109.133.133> (permalink) |
Scott Sauyet <scott.sauyet@gmail.com> wrote on 10 jul 2014 in comp.lang.javascript: > Evertjan. wrote: >> Andrew Poulos wrote >> >>> I've found window.matchMedia and together with addListener (given I'll >>> need to work around the lack of support for it in IE 9) I should be able >>> to track the "visibility" of the things that need tracking. >> >> The visibility does not mean you can see the element. >> You will first have to define visibility as something else, >> perhaps having the CSS style visibility as not hidden, >> and the css style display as not none, >> and z-index not making the element below an other one, >> and ... ad libitum. >> >> All this is not javascript related. > > With the OP's discussion of "tracking" the visibility, presumably > the values of some of these properties can change dynamically. If > that's the case, then I think this is very much the domain of client- > side Javascript. As I say below, the dynamics of the page could be done by javascript, or by pure css, or by manually changing the window size, but should be fully designed by the code and the specs of the browser. >> However if you programme consistent html cum css, >> you will know if an element is visible, >> there is no need to "track". > > Only if those properties remain static. Not at all. The dynamics of a page are fully defined by the programming, and you can "compute" the effect at any moment. -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress)
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Element visible Andrew Poulos <ap_prog@hotmail.com> - 2014-07-09 10:09 +1000
Re: Element visible Andrew Poulos <ap_prog@hotmail.com> - 2014-07-09 13:32 +1000
Re: Element visible "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-07-09 09:54 +0200
Re: Element visible Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-07-09 11:18 +0200
Re: Element visible Andrew Poulos <ap_prog@hotmail.com> - 2014-07-09 23:17 +1000
Re: Element visible John Harris <niam@jghnorth.org.uk.invalid> - 2014-07-09 16:08 +0100
Re: Element visible Andrew Poulos <ap_prog@hotmail.com> - 2014-07-10 10:07 +1000
Re: Element visible "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-07-10 09:15 +0200
Re: Element visible "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2014-07-10 10:45 +0300
Re: Element visible Andrew Poulos <ap_prog@hotmail.com> - 2014-07-10 22:13 +1000
Re: Element visible "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-07-10 14:31 +0200
Re: Element visible Scott Sauyet <scott.sauyet@gmail.com> - 2014-07-10 13:35 -0700
Re: Element visible "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-07-11 00:23 +0200
Re: Element visible Scott Sauyet <scott.sauyet@gmail.com> - 2014-07-12 20:09 -0700
Re: Element visible "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-07-13 09:07 +0200
Re: Element visible John Harris <niam@jghnorth.org.uk.invalid> - 2014-07-10 10:46 +0100
Re: Element visible Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-07-10 12:10 +0200
Re: Element visible Andrew Poulos <ap_prog@hotmail.com> - 2014-07-14 13:00 +1000
Re: Element visible Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-07-15 15:08 +0200
csiph-web