PUBLIC MARKS with tags bug & css

On a recent project for a client we experienced the well known iOS5 bug with fixed positioned elements not actually being where they are rendered. This happens after a programmatic call to window.scrollTo()

On a recent project for a client we experienced the well known iOS5 bug with fixed positioned elements not actually being where they are rendered. This happens after a programmatic call to window.scrollTo()

"loading scripts and stylesheets in the typical way creates a frontend single point of failure that can bring down the entire site"

"Making Internet Explorer think a certain box "has layout" can correct most of the float-induced or list-related bugs found in that browser."

Nouvelle version du fix pour les png sous IE6 qui supporte enfin les background répétés et/ou positionnés !

Without a doubt, a logical and structured layout is the best way to go. Not only because your layout varies between browsers, but also because CSS has a lot of ways to position every element you have. Today we wanted to share with you some quick tips on how to avoid easy pitfalls when creating your CSS layout. This is the first part in this series as there are SO MANY good tricks out there and if you see an easier or better methods, then post a comment below or email me. I will do my best to include it in our next post in this series.

euh, le bug du jour. je suis tombé dessus ce matin. => il peut arriver que ie6 buggue quand dans son code HTML on a : 1. postionné des éléments en fottant 2. mis des commentaires HTML ! J'ai cru devenir fou jusqu'à tomber sur cet article. Ce bug a bien été identifié.

le problème des espaces verticaux dans les listes sous IE à cause des sauts de lignes dans le code source (solution plus simple, ne pas coller de saut de ligne dans les li)