Archive for April, 2008

I’ve recently decided to take a break from web development probably for a couple of months. One of the reasons for this is that I’m starting to feel very burnt-out (I haven’t had a break for more than a month in three years), and the time has come to get a change of scenery for my own sanity!

My tasks for my time off are as follows:-

1. Get super fit like I was a couple of years ago before a little thing called ‘work’ came along.
2. Go visit my mates who are at uni
3. Do some local voluntary work; I really want working with people who aren’t as fortunate as me to give me a more rounded view on life, ‘cos I kind of take life a bit for granted at the mo, but I want that to change…

Note to spammers – I can understand you’re eager to post your unrelated links on my posts, but please can you refrain from doing so for the next couple of months? I won’t constantly be at my desk like I’ve been up until now, so will be unable to remove them as quickly – thanks!

So finally, please don’t expect many (if not any) new posts to appear on the site – I wish you all well, and hopefully see you all back here in a couple of months!

Following on from the recent CSS WG F2F where issues relating to the concept were either resolved or noted, and from some email correspondence with Dave Hyatt, I’ve carried out an update to the article.
CSS3 ‘box-sizing’ article

A recent post on CSS3.Info regarding the CSS WG F2F in San Diego nicely sums up resolutions relating to possible up-coming CSS features.

Two resolutions that the post doesn’t mention however, are to do with the public disclosure of dialogue within the Working Group relating specifically to IRC log’s and meeting minutes.

It was decided that from now on the WG’s minutes and also IRC logs will be made public; there was also talk about opening up process-related discussions into a new public mailing list, although this has apparently been put on the back burner for the moment.

What I feel this does show is that the WG are listening to what people are wanting and have made their workings more transparent, which is great news.

Here are the first minutes

Just noticed this…

….and this font-size inconsistency (Safari 3.1 overlaying FF 2.0.0.12), both in OSX

Look’s like a couple of regression bugs as they certainly weren’t there in 3.0- think I’ll need to come up with a test case or two.