View Single Post
Old 06-29-2009, 03:31 PM   #68
netseeker
sleepless reader
netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.
 
netseeker's Avatar
 
Posts: 4,763
Karma: 615547
Join Date: Jan 2008
Location: Germany, near Stuttgart
Device: Sony PRS-505, PB 360° & 302, nook wi-fi, Kindle 3
Quote:
Originally Posted by llasram View Post
@netseeker: Sibling selectors mean that you need to keep the whole parse tree around to figure out the CSS rules which apply to a particular element.
No, definitly not for siblings in general. I guess you mean adjacent sibling selectors because the CSS 2.1 specification contains nothing about "sibling selectors". Adjacent sibling selectors mean that you need to know at least the current node and it's predecessor.
netseeker is offline   Reply With Quote