All seats have been taken. Please write a comment to be put on a waiting list, there are always a number of cancellations, so there’s still a chance.
Time for another Geek Meet! If you’re not in Stockholm, you should make it here!
The last week I’ve been contemplating whether to write anything or not about the situation with web browser vendor prefixes in CSS. I decided to share my thoughts on the problem and possible solutions.
It’s been a while since I last shared some good reading, but hey, it’s 2012 now, so I thought I’d share my first batch this year!
Last chance to share some good reading with you before the end of 2011. Some good ones in here!
I will soon start blogging more here again, now that time permits – for now, however, I’d like to share a round of good links I’ve collected recently.
Time again for a number of interesting, entertaining or otherwise all-round good links I recommend taking a look at!
I took a little hiatus last week from posting Robert’s read, but now it’s back with lots of good links!
Yesterday I had the pleasure of speaking at the London Ajax Mobile Event in, surprisingly, London.
Today I was just about to write a blog post about images and serving different sizes depending on the device accessing it. Then the Adaptive images post came up on the public-html@w3.org mailing list. So let’s look at that and add my thoughts.
HTML5 is here to save us all: it has the cool functions, eye-dazzling features and APIs to go around. I get to see a lot of great things developed with HTML5, but I’d like to issue a word of caution as well.
I’m currently in Las Vegas for Microsoft’s MIX conference where they just showed the first version of Internet Explorer 10. Given what they announced, I have some thoughts.
Geek Meet is now sold out! Please write a comment to be put on a waiting list. Please note that usually everyone on the waiting list eventually gets a spot
Time for Geek Meet May 2011! This time, welcoming a great speaker from Greece!
I wrote about it on Twitter last week (follow me on Twitter!), but naturally I should mention it here too, my dear readers. With new input from testing Internet Explorer 9 and from the Opera team, I have updated my HTML5 tests and compatibility tables and CSS3 tests and compatibility tables.
I should have written about this long ago, but better late than never – time to share my experiences. Typography is an important part of user experience, and with CSS3 @font-face we can offer users any font we want to.
Doing layouts on the web has always been hard, but it seems like we’re getting a better option to do it now.
With the myriad of devices, web browsers and screen sizes out there, we need a way to to be able to easy detect how we want to layout a web page for them. This is now offered to us through Media Queries in CSS3.
I recently wrote about CSS3 Transitions and the next step for that is sort of CSS Transitions on steroids: CSS3 Animations (CSS Animations Module Level 3 specification).
The other day when I wrote Using CSS3 Transitions To Create Rich Effects I was thinking of nice ways to apply this. One of the things that came up was creating the Mac OS X Stacks behavior entirely in CSS!
There has been discussions about allowing CSS to help developers create smooth transitions of CSS properties for elements, and it’s something being specified in CSS3 in W3C CSS Transitions Module Level 3. Here I’m going to show you how to implement it in Firefox, Google Chrome, Safari & Opera.
As an Interface Developer, it has always been a challenge to make the designers’ dreams come true, especially when it comes to shadows, gradients and various level of transparency. Slicing images till no end, trying to make it look good. Nowadays, though, a nice alternative is to do it with CSS.
Ever placed an element on top of another element, but wanted the one under to be clickable? Now it’s doable, with CSS pointer-events!
At MIX10 yesterday, Microsoft announced IE9 and spoke about its upcoming features. And, lo and behold, they released a Internet Explorer Platform Preview for anyone to download and play around with!
One of the most common CSS effects is using shadows in various ways. Before, we needed to resort to images, but now we can offer this to all major web browser with CSS!
One thing I have always pondered about is whether elements that are hidden will load any images associated with it, either inline or through CSS, directly at page load. And apparently, my colleague Jonatan Larsson has as well.
Usually when you want a horizontal list, you need to use float in the CSS code to make it work, with all its drawbacks. However, there is an alternative with display: inline-block.
I think we can all agree that performance of web sites matters a lot, and slow web sites are very annoying both for developers and, more importantly, end users. Therefore, we need to talk about a newly discovered problem: Internet Explorer, protocols and inclusion of stylesheets.
One thing that is quite nice is that we now have the ability to create gradients in our pages just from CSS code, and without the use of any images.
To follow up on the topic of cutting down the number of HTTP requests that I mentioned in my posts How to improve your web site performance – tips & tricks to get a good YSlow rating and How to reduce the number of HTTP requests, I wanted to put together a good list of tools and approaches to concatenate and minify CSS and JavaScript files in different developing environments.
As you might be aware of, I believe web site performance is truly a critical success factor, and I have written about it before in How to improve your web site performance – tips & tricks to get a good YSlow rating
Looking at the design of most web pages today, almost exclusively all of them include some semi-transparency of elements. However, getting the desired effect in CSS is harder than one might think.
Let’s face it: developing CSS that should work across various web browsers and platforms is hard, and could prove to be quite a challenge. This is where Object-Oriented CSS (OOCSS) steps in.
It seems like Apple is about to go down a road which is completely against the spirit of the web.
Last weekend, I had the pleasure of being invited by Mozilla to Prague to, amongst other things, discuss the future of Firefox.
When I released Firefinder back in May, I had some ideas with what more I wanted to do with it. Now I can happily say that I have implemented those ideas!
Firefox 3.5 was released yesterday, and it has already reached 5 and a half million of downloads (at the time of writing). Therefore, I thought I’d answer some common questions, especially from a web developer perspective about the new version and which web developer extensions which will work with it.
Yesterday we had Geek Meet Charity in Stockholm, and in my opinion, it was a great success!
In my day job (i.e. the one paying the bills), I encountered a very serious problem in Internet Explorer, which turned out to be a show-stopper in my current project.
I am very happy to say that an idea I’ve had for a while has finally been implemented: Firefinder for Firebug.
This proposal might seem a bit drastic, but please allow me to present my case.
I have just released a new version of my Firefox extension Inline Code Finder and made a personal download record! 🙂
Yesterday, IE 7, once again, pushed me to the brink of going postal. Refusing to give up, I finally managed to find the problem.
I remember it like it was yesterday: my first hex code! 🙂
Admit that you have always wanted to know how to develop a Firefox extension but never had the time to learn. 🙂 Here I will walk you through and at the end of the article we will have created a fully functional Firefox extension!
When I first coded and released Obtrusive JavaScript Checker, I had some more ideas with it, as well as some great feedback I have received and wanted to see to. The result is Inline Code Finder, which looks for inline styling as well as what the Obtrusive JavaScript Checker offered, and it comes in two versions!
Something was brought to my attention which, to say the least, left me a little baffled: IE 6 is coming to mobile phones…
When I review web sites, and also in my own projects with a number of different team members, I almost constantly stumble across something web developers should really refrain from: inline styling and inline JavaScript code.
Yesterday I ran into a little unexpected behavior when adding title attributes to a couple of link elements.
This article is also available in Hungarian.
Personally, I like opacity when it is used well in a web site. And instead of some static images, I prefer, when possible, that it is achieved through CSS.
Many people ask me how I choose to address an situation where all content in a web should be available without JavaScript, but certain parts hidden if JavaScript is enabled.
We all heavily evangelize the validating of HTML code and think it’s just a given, right? But how about the CSS code?