78. Thank you.
Slides and resources: http://wp.me/PorPc-9d
Photo credit for Media Queries example: http://www.ﬂickr.com/photos/dominicspics/4625808875/
Font for web fonts example: http://www.yanone.de/typedesign/kaffeesatz/
I&#x2019;m Rachel Andrew. You can find me on Twitter @rachelandrew and the links here are to my personal and business sites if you want to know who I am. The important thing is that I&#x2019;m a front and back-end web developer and spend my days actually using the stuff I&#x2019;m going to be talking about today on commercial projects for real clients. So I tend to take a pretty practical approach to it and feature the things I feel are useful right now.
This session is Core CSS3 - so in the next 40 minutes or so we&#x2019;ll have a look at CSS3 with an emphasis on things we can use right now. Don&#x2019;t worry about taking notes or copying down code - I&#x2019;ll give you a link at the end of the presentation where you can download slides, example code, and any links for examples.
So what is CSS3?
Fairly obvious - CSS3 is the next version of CSS.
Earlier versions of CSS were a single monolithic spec. CSS3 is different - it is broken down into modules.
Modules are at different levels of completeness and slower, more involved modules then don&#x2019;t hold up other parts of the spec.
Working Draft (WD)
A Working Draft is a document that W3C has published for review by the community, including W3C Members, the public, and other technical organizations.
Candidate Recommendation (CR) - gather implementation experience
Proposed Recommendation (PR) - sent to the W3C Advisory Committee for final endorsement.
W3C Recommendation (REC) -specification or set of guidelines that, after extensive consensus-building, has received the endorsement of W3C Members and the Director. W3C recommends the wide deployment of its Recommendations.
Browsers have been implementing parts of the CSS3 spec for a long time.
Firefox, Opera, Safari, Chrome etc. all offer support for many different parts of the spec.
Vendor specific extensions are one way that browser manufacturers started to implement CSS3 at a very early stage of some modules.
We&#x2019;ll be looking at this in detail later but border-radius (which gives us rounded corners in pure CSS) is one place where browsers implemented support with their own extensions.
The 1st line is how Mozilla implemented this in Firefox when the module was at a very early stage, the 2nd is the webkit extension for Safari and other webkit browsers (including Chrome). Safari 5 - just out - has added support for the standard border-radius. The last line here is the actual CSS3 border radius property.
If using a Vendor specific extension always add the actual CSS3 declaration as well. For example when IE9 comes out it will support border-radius, if you omit it now from your CSS then IE9 won&#x2019;t show the rounded corners even though it would be able to.
a W3C approved way to add extensions
Usually added at an early stage of module development
If the module changes the browser doesn&#x2019;t need to change their implementation thus breaking older code.
Use carefully and keep an eye on the actual spec and correct way to do things.
I&#x2019;m now going to take a look at some practical examples of CSS3 - things that I&#x2019;m currently using in real sites.
In CSS 1 and 2 we had selectors that let us target things such as html elements - h1, h2, paragraphs, divs and also classes and ids.
Often have to add classes just for the CSS - for example a class on the last item on a list
Annoying when we can access the mark-up, doesn&#x2019;t help separate presentation from content & structure
Sometimes we can&#x2019;t access the mark-up - generated by a CMS we can&#x2019;t change etc. and then we end up having to lose bits of a design because we can&#x2019;t do them without adding classes.
CSS3 selectors will just make our lives so much easier - both for front and back-end developers.
first-child actually appears in the 2.1 spec however lack of browser support in older versions of IE means it doesn&#x2019;t get a lot of use. It&#x2019;s a nice easy way to start looking at more advanced selectors however.
We have a set of paragraphs -these are inside a div with an id of wrapper.
With CSS2 we would need to put a class on the first para in order to style it differently.
As this screenshot shows - the CSS we used means we can target that first paragraph and make the text larger without needing to add anything to the mark-up.
Introduced in CSS3
An example where last-child might be useful is when styling list navigation. The li elements have a bottom border but we don&#x2019;t want to put that on the last element.
As you can see this removes the border just from the last li in that list - once again we don&#x2019;t need to add any additional elements to our mark-up.
We have a table here and the designer has requested that we colour every other table row to aid readability. This is a common request and usually means the developer has to put a class on the odd rows.
Here are our odd rows all coloured as requested, with no additional mark-up.
nth-child can take arguments using a multiplier in addition to odd and even keywords. Using the multiplier 2n+1 would be the same as using the keyword odd. These multipliers get a bit complicated and I would suggest having a look at the listed Sitepoint resource to get your head around how they work as they can be a very powerful way to taregt elements in your mark-up.
The selectors we have looked at are all &#x201C;structural pseudo-classes&#x201D; they look a bit like the other pseudo-class selectors you may be familiar with - the ones we use for the different states of a link - link, visited, hover and active.
Time limits me from looking at too many selectors today but another group of selectors that are very useful are known as combinators. We have things like an adjacent sibling combinator&#x2019; selecting an element that is next to another element that shares the same parent. So the p that comes straight after an h1 for example.
This rule would make the first paragraph directly after an h1 larger in this example.
Attribute selectors were also part of CSS2.1 however lack of browser support has meant they are not much used. However as they are also part of CSS3 and very useful in our aim of not cluttering mark-up with classes we&#x2019;ll have a quick look at them.
Attribute selectors let you get at an element based on it&#x2019;s attribute. An obvious use for these is in forms. If you just target input you get text fields, submit buttons and checkboxes etc. This usually means we stick classes on all the input elements to distinguish them. Attribute selectors let you look at the type attribute of the input element and style appropriately.
There are two other things I have used attribute selectors for in this example. The labels have been styled floated left and given a width - which I don&#x2019;t want to do with the checkbox label.
I also wanted to display and email icon next to the email us text.
So I&#x2019;m using the for attribute on the label to check for the label of that field and setting it to float none and width auto.
To get the email link we use the second declaration - ^= shows we want to match things in the href that begin with mailto
So before we get too excited about this - what about the thorny issue of browser support? If you know a bit about CSS3 and aren&#x2019;t using it right now it is probably because of the requirement to support more browsers than just those that have support for these selectors already.
as you can see things look great if we look at Firefox, Safari, Chrome and Opera ... not so stunning when it comes to Internet Explorer. Even the most recent release of IE8. A couple of selectors we looked at that we part of CSS2.1 (attribute and first-child are supported by IE7 and 8) Things look up when it comes to IE9 which promises to support a lot of CSS3 however what can we do now?
The first thing to check is &#x201C;does it matter&#x201D; that Internet Explorer sees something a bit different. In a very few cases you might feel happy to just fall back to allowing IE to not have striped tables, larger initial paragraphs etc.
For most of us though, our clients would expect the site to look pretty much the same in IE8 as in Firefox so what can we do?
This is an example of how you can use jQuery to add support for first-child. Add a class to your rule for p.first then select the first-child using jQuery (which supports the CSS3 selectors) and add the class.
Here is the same technique as used for last-child
and nth-child. JQuery makes this very easy but you could do the same using any library you are already using on your site.
IE-CSS3.js - selectors only, needs a library included as well
ecsstender - several extensions for different modules
Color module - properties that allow authors to specify the foreground color and opacity of an element
Opacity effects the entire element and it&#x2019;s contents.
The boxes have been given an opacity value, we are also using the hover pseudo-class on the list item to change the opacity on hover.
Should be noted that opacity effects everything in the li including the text.
The color module introduces RGBA
I needed to get a photo of my cat in here somewhere... the caption on this photo has a semi-transparent background which is implemented using RGBA. I didn&#x2019;t want to use opacity as that would have made the text opaque as well.
The 0.5 is an opacity value on the background colour. 0 would be transparent 1 would be fully opaque - a solid colour.
See an example of RGBA being used extensively on the design for 24ways.
Neither opacity or RGBa are supported by IE up to version 8. If using RGBA you should specify a color using rgb before the rgba line in your CSS in order to provide a fully opaque version - without this no colour will be used.
One thing that web designers have longed for is the ability to be able to specify particular fonts and know that users will be able to view the site in them.
@font-face enables the importing of a font that you have uploaded to your web server - then that font can be used in your font stacks just like any standard font.
In theory this should work like this. The @font-face rule points to the font file with a familiar url construct. You can then use it. In the real world however things are not so simple... we have two problems, different browsers and operating systems and the licensing of fonts. Many fonts you will find are not licensed in such a way that you can upload them to your web server, presuming you have a font that is able to be licensed. You can do the following:
Upload your fonts and Font Squirrel will create a package of fonts that will work across all major browsers.
You will end up with a fairly terrifying looking @font-face declaration but it will contain font files that work well cross browser.
Using a hosted font from typekit
Background and borders module
So here is something that should make a lot of people happy. The CSS3 backgrounds module allows for applying multiple backgrounds to a single element.
so on this blockquote element I can add image quote marks as a background at the top left and bottom right of the element without needing to add an extra element.
...which gives us a result like this. I&#x2019;m sure you can think of lots of uses for multiple background images.
So it is probably against the law to do a CSS3 presentation without mentioning rounded corners so here they are. The backgrounds and borders module includes the spec for adding rounded corners to an element.
As of Firefox 3.6 FF supports multiple backgrounds as do recent versions of Safari, Opera and Chrome. Rounded corners are supported by all these browsers as well.
I want to wrap up this introduction to the useful now bits of CSS3 with a quick look at media queries. The great thing about media queries is that the place where they are most useful - we already have good support.
Media queries let you target browser characteristics such as screen resolution and provide alternate styles. If you have ever created a print stylesheet the concept of creating a whole new stylesheet or overwriting some existing styles should be familiar to you.
Where this is very useful today is if you want to create a version of your site for the iPhone or other devices that support media queries. A device running an up to date Webkit, Opera or Mozilla based browser should have support.
Here is the code that creates a two column layout.
It looks something like this in Safari or other browsers. I have decided that for iPhone and other small device users I would like the big image at the top to be smaller to reduce scrolling and the layout to drop to one column with the main content at the top.
so this is the code that detects the screen width of the device and resizes accordingly. The important bit is that which I have highlighted in yellow. So here we are in our main stylesheet or in style tags at the head of the document in my example just to keep it all in one place. This lot comes after the main screen CSS so overwrites them if the user has a device with a max-device-width of 480pixels.
So we get something like this.
I could also have 2 stylesheets and link the appropriate one using this link syntax. In practice I&#x2019;d probably go for this approach as it seems neater to me to have the different styles in a separate stylesheet and I like the maintainability of it. If you only have a few changes to make though you could do them inline as previously demonstrated.
example site using media queries in browser
example site on iPhone. Even if you feel that a lot of CSS3 isn&#x2019;t possible for you to use for your sites and clients right now, I&#x2019;d really encourage you to have a look at media queries. With just a little bit of CSS you can have customised views of your site for small screen devices - a special iPhone version just thrown in for free as far as your clients are concerned. Definitely worth trying out.
So that about wraps it up. (Check time for questions). Later on today or this evening - wifi permitting - I should get my slides, some resources, and example files online at the above URL - I&#x2019;ll also post to my blog once they are up at rachelandrew.co.uk.