Skip to main content

CSS Selecting elements that are immediate children only

I have been working on my integration skills recently with @Trullock  and have been really enjoying it. Coming from a foul tables background and not really looking at much CSS for a couple of years has left me in a bit of a rut. Especially when it comes to integrating from a proper design from scratch and not just pinching bits from all over the place. I will try and publish some more little gems I have been shown when I get round to it.

I was quite pleased with this CSS Selector. We used this both in the CSS and for getting a hold of things in JQuery.

When you want to select only immediate children of a class, id or element you can use the following:

.parent.child /* For immediate children that are classes... */

/parent > ul /* For immediate children that are elements... */

This will then stop the browser / jquery looking further down the tree and wasting time, memory and potentially finding something you don't want the style to apply to or JQuery to get hold of. 

This might be obvious to some but it was a nice little tip for me!




Popular posts from this blog

NESTA - Next Gen.

via Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt

Reigniting posterous again perhaps

I'm taking another look at Posterous again. I'm not really sure why as I haven't written a proper blog for a while but this seems an easy way to share between all my other tings...