Css

Articles like this one and initiatives like “pre-fix the Web”, aim to highlight to web-developers how important is to build a cross-browser web. The importance of such a point has been explained in so many places, there is no point in me saying anymore. People like Tim Huegdon can give you a far better lesson on this. But if you are after a “one sentence to blame them all”: If you write a website caring only to test it on WebKit based browser (worse, only your iPhone!!!), you are a MORON. ...

Hi. I don’t know if you can notice it, but I just did few updates to the CSS of this Blog. Effects of sleep deprivation (no, I’m not THAT tired) If you are one of the few a followers of my Bloggart fork, you know what’s going on: Page support, changes to the “Squared” theme and more. I’m not yet where I want to be, but it’s getting closer. While I add small features to Bloggart, I learn its intricacies, and discover some small/medium latent bugs. Stuff that “didn’t happen because scenario x was never considered”: this is giving me some possibilities to fix and improve. ...

This is a set of commets to some of the asserts made by Steve Jobs in his Thoughts on Flash. Safari has just ~5.5% of web users share […] Apple even creates open standards for the web. For example, Apple began with a small open source project and created WebKit, a complete open-source HTML5 rendering engine that is the heart of the Safari web browser used in all our products. WebKit has been widely adopted. Google uses it for Android’s browser, Palm uses it, Nokia uses it, and RIM (Blackberry) has announced they will use it too. Almost every smartphone web browser other than Microsoft’s uses WebKit. By making its WebKit technology open, Apple has set the standard for mobile web browsers. […] Ehm, what about Netscape Gecko? It’s not just Firefox and it’s share of web users, much larger than the one of Safari, but also the fact that the Mozilla Foundation is very much involved in building (W3C) standards like HTML5 et similia. I can see that you used the word “Almost”, but that’s not a good start: Steve, let’s try to be more fair here. ...

As I said, I’m doing some stuff with Google AppEngine. And, of course, I’m facing the usual problem of Browser Incompatibility: Browser Incompatibility ;-) =Browser Incompatibilities: the Most Common Problem= The most common problem for Web Site developers is the fact that every browser treats HTML Tags, CSS and Javascript in it’s own way. This Recipe tries to address one of the problem I faced the most: having a slightly different CSS for every Browser. =The Usual Solution= The usual solution is to load every time a different CSS depending on the Browser. But this solution has some side effects: ...