Archive for the ‘web’ Category

IE7 and Firefox 2 : headaches for web developers

December 3, 2006

IE7 and Firefox 2 are now released and begin to spread in the world thanks to auto-updates and the cool factor driving technology.. What does this bring us? Well.. happiness and sleepless nights..

Happiness: IE7 is coming with a bunch of features and bug fixes that allow us to think of a bright future where browsers co-exist in peace without making web developers struggle too much for delivering their cool web pages..

Sleepless nights: as described in previous post about CSS design patterns, a lot of websites rely on web browsers bugs for writing browser dependent rules in CSS. As there are (were?) still differences in browser rendering, CSS cant yet be written in independent manner. But with IE7 supporting fixing bugs and supporting CSS 2, all these rules become obsolete and rules written for firefox are now going to be applied to IE7. In some case it will work but we can expect a whole lot of websites designs that will break in the following weeks and months..

The second issue comes from the support of SSL in IE7 and FF2: they only support SSL version 2, which means that servers implementing SSL V1 wont work.. It sure going to involve some time fixing this issue..

But well, crises are meant to make us humain being evolve for the better, arent¬† they ūüôā Good luck for everyone involved in web development and enjoy the new tools…

PS. for a solution on how to¬†safely manage browser dependent rules in CSS, check previous post…


CSS design patterns for web 2.0

November 26, 2006


Summary: web 2.0 has seen dramatic changes in the way pages are developed. CSS standards are evolving to cope with the demand but in todays browsers web 2.0 requirements have outgrown CSS features and very few strategies are either defined or applied by CSS developers in the web industry. This makes web page creation a kind of black magic that is both expensive and risky as magic tricks might not work in next versions of browsers. This article describes the situation and provides 2 design patterns that make a significant change in developing web pages with direct returns on

  • css code reuse
  • quality,
  • safety of investments
  • ease of development and support of browsers.



As the web technology progresses on the client side with Web 2.0 being spread in the industry, we rely more often on both javascript and CSS for building websites and web applications. Whilst the javascript side is fairly well covered on the design side, with the knowledge derived from JS libraries (prototype.js, dojo, Y! UI, G! UI, etc.), we still don’t see enough efforts to rationalise CSS development (yes I know it’s a bold statement, but well just a view from my little corner, and anyway, I like bold statements :-).

We know that browsers are getting closer to each others in terms of CSS support. Thanks to Mozilla, we now have a decent cross platform browser that we can spot on our traffic analysis graphs without a magnifier. That means we now need to support more than one browser and it is a lot easier than it was with the evil Netscape 4 or Mac IE. But there are still some issues CSS developers (yet another title to put on already heavy CV in the industry) have to face nowadays…

First issue: font sizes and accessibility

By law, respect or any other reason, fonts in web pages that are written these days should scale well so that everybody can read them. To have fonts that scale well in all browsers, we should use units such as “em”, “%”, or “small/medium/large”, instead of “px” (pixels). However it is very difficult to use these units because:

  • “em” or “%” units are dependent on their context (what is the current font size), so any change in html or css can (and does) have side effects on other parts of the page. I know  it is possible to write pages like that but it is not easy and it is risky.
  • “small/medium/large” are the easiest and natural way of writing fonts that will scale well in any browser/device. However Mozilla, for probably a very good reason (what is it ?), displays fonts that are smaller than on any other browser. This breaks the design..

Conclusion: we can’t write accessible web pages with only a clean cross-browser CSS sheet.

Second issue: managing z-index

A lot of web applications now use drop-down menus or other widgets that display on top of others. In CSS, z-index property defines which layer should go on top of the other. Well, not always as IE has a bug for elements that are relatively positioned. It then breaks the rules and we have to apply special tricks well described in .

“height” matter

Not all browser support height properties the same way. IE6 allows to use the CSS “height” property for most html tags, whist in Firefox, the “height” is only supported (as defined in CSS standard) for block elements, and in any case, most of the time it is “min-height” that is equivalent to IE’s height .

Conclusion : getting the right height in CSS involves some kind of trickery to make every browser happy, and to play with “height”, “min-height”, line-height”, “padding” etc. until we get the right result in all browsers (whatever “all” means for you :-).

Lack of CSS reusability

HTML and CSS is often used beyond their limits and new de facto standards are created in this outland area. Examples are:

  • transforming ul/li lists into menus
  • creating side areas with floating divs (replacing tables).

Achieving these effects is not very easy because they use html/css features that were not designed for these purpose. The “float” property was mainly used to have floating text around images, not for replacing tables or create css menus. Although this works fine, CSS development is then quite difficult to write and then is more expensive. Also, because design pattern for reusability are not well known for CSS (apart from reading tutorials and rewriting things from scratch), we haven’t much CSS libraries on the market. Web development tools can help in some cases but not enough for making things any better.

Conclusion: CSS development is tedious and expensive because of lack of reusability and skill levels required.

Lack of common support for javascript behaviors in CSS

One design pattern that provides a direct impact on programming quality, time/money spent on projects of medium size is the “Model-View-Controller” or “MVC”. The basic idea is to separate things so that development can be done in parallel by different people (ex. graphic designer/html developer/javascript specialist/PHP developer/etc.). There are many other quality factors brought by this model (reusability, testing, maintenance, etc.).

In web2.0 applications, we can see components being implemented in web pages (ex. calendars, menus, other widgets, etc.). Modular Javascript libraries are available for helping in the development of such components, however it is still difficult to truly separate html from javascript the way html and css can be separated. The reason for that is we often need to attach a “behaviour” (such as opening a new window, adding a visual effect, etc.) to a piece of html and/or add html fragments in some specific parts of pages. To do so, we need to add <script> tags in the code. This solution is not very effective because html/css developers can’t write the page without either knowing javascript or work with javascript developers. This costs time and money and makes pages difficult to modify.

One excellent way to attach javascript behaviour to html is to put the attachment in a css rule. ex. { behavior: } . This example use IE syntax for attaching a javascript component (HTC) to html. Mozilla has another syntax for behaviours. The main issue is that we can’t use them because they are browser specific (and also some browsers have no support at all for behaviours).

Several workarounds have been added to js libraries but they are cumbersome, fairly slow and/or break the (x)html standard:

  • parsing the DOM and add behaviours to html elements with a specific css selector: cf. “behaviour.js” or “prototype.js javascript libraries.
  • parsing the DOM and add behaviours to html elements with a specific attribute. ex. dojo library with its “dojoType” attribute.
  • add XML tags in the html code and transform by js into components (ex. dojo tags <dojo:widget />)

These solutions are good enough and the best ones we have available but they can make page loading a bit slow. If a standard for web components was defined and supported in browsers, we would probably see a lot more reusable components on the market…

No Support in CSS for selecting rules by user agent

Because of several cross browser differences, CSS sheets have to be written in browser dependent manner.  How can this be achieved? As nothing in CSS currently helps in writing CSS rules dependent on the browser application (apart from “screen”, “print”, “tv” devices selectors for <link> tag), developers are using black magic based on application bugs or CSS level support:

  • some funny sequences of characters make a rule or part of the rule work in some browsers and not in others (ex. \*//*/ for IE/Mac)
  • conditional compilation in html is supported in IE (in html only)
  • IE6 doesn’t support the “>” parent syntax (as in ul > li), so rules written with this syntax wont be used by IE.

The fact we have to rely on bugs in internet browsers makes the development of pages both difficult and risky. Difficult because these tricks are not easy to achieve and are poorly documented. Risky because bugs could be fixed (we have seen these things happening, even in IE). So in next versions of IE or Firefox we could see a lot broken designs in websites… This could lead to some decent amount of money spent in fixing these websites. It actually reminds me of the huge work involved in fixing applications in year 1999 for supporting Y2K. Or business applications when the euro currency was launched in Europe…

Proposed solutions and design patterns

Solution 1: adapting standards and browsers to the reality of web 2.0 development.

The ideal situation would be to have CSS standard following the development reality by:

  • adding CSS selectors based on the user agent and/or browser application. It could be for example:
    gecko: body {font-size:small;} ie.5+ {font-size:x-small;}
  • or have CSS selectors based on supported features (css2: ul>li {})
  • create standard JS components via css behaviors.


Design Pattern 1: add support for browser dependent rules (without relying on browser bugs)

One way to distinguish rules supported by a specific browser is to add a class selector of the form: li { position:relative;z-index:100; }, body.ie_mac {position:static }.

Classes derived from the user agent can be added to the body tag at load time.

example (dependent on prototype.js):

// add support for user agent detection in document
Object.extend(document, {
getUserAgentClass:function() {
if (window.opera)
return “opera”

if (/MSIE/.test(navigator.userAgent)) {
if (/Mac/.test(navigator.platform))
return “ie ie_mac mac”
return “ie ie_win win”
if (/Gecko/.test(navigator.userAgent)) {
return “mozilla”
if (/Safari/.test(navigator.userAgent)) {
return “safari mac”
return “”

setBrowserClasses: function() {
// add user agent to body class

// add UA classes to body
Event.observe(window, ‘load’,document.setBrowserClasses);

NB. by applying this method, we make sure that CSS rules will be safely applied to a specific browsers and that these pages won’t break when browser bugs are fixed or when a new version is launched… This also makes CSS development easier and faster, in the short and long terms…

Design Pattern 2: use an modular/OO approach to CSS

CSS libraries can be implemented by using two interesting features in CSS:

  1. the ability to add several classes to an html tag. ex. <ul class=”horiz_list menu”><li>etc.. </ul>
  2. filtering CSS rules by a selector: ex. .horiz_list ul li {float: left;}. This feature limits the impact of defined rules to only a part of the DOM, thus avoiding side effects to other html parts in the page.

Combining these 2 features allow HTML/CSS developers to create CSS libraries that can be directly reused with less risks of having side effects. In the example above, the horiz_list class is applied to a <ul><li> to make it a flat list. The actual design for the menu (colors, fonts etc.) can then be defined in “menu” class, thus making it very easy to develop horizontal menus…

This example can be applied also to javascript components: separating the design of components (colors etc.) from their function (horizontal menu). We can then share CSS libraries across projects and people and make the creation of web page less tedious and expensive…


Developing CSS based pages is still difficult, expensive and risky because no actual design patterns or development standards are widely available or used by web developers. This could be easily improved by sharing the knowledge of CSS gurus (such as the guys at Zen garden and many others) into reusable CSS libraries or design patterns. This would help the web industry in getting better development quality at lower costs. The 2 design patterns described above could help achieving this objective and I hope that others will be available and applied in a near future…

Google widgets and Office2.0

October 18, 2006

Google has released a new API for integrating its wdgets in any website. !!!!!!

Which impact can we expect from this news?

On the short term, probably not much except in personal home pages as most of these widgets are “cool” but not very useful, at least for commercial websites. It is unlikely we see these widgets soon on corporate portals, except maybe for some of them like map searches, etc..

However the impact will probably be to awake the web to this type of technology which is:

  • a piece of information displayed in component made of¬†html and javascript (easy to write),
  • this type of component can run on the desktop, in a website or on google portal.

Obviously we don’t really want to include google stuff everywhere, but when product developers realise that they can apply the same type of technology for THEIR own components, then we can expect that the next wave, right after AJAX, will be based on a¬†type of architecture where the content can be freed from website pages. Pieces of content will appear simultaneously:

  • in collaborative websites where users can manage them in a central place,
  • on desktops in widgets frameworks (google/Y! etc.) : so that we can be notified of any new article without opening the website (convenient as side popups can display news without distracting too much user’s attention)
  • in other syndicated websites: similar to RSS feeds which allow content notification to be displayed in RSS readers thus increasing the visibility of¬†the content. We could also with this technology foresee¬†websites exchanging applications modules as a kind of marketing tool. Content syndication will then not only be limited to xml or text forms but will include applications as well (just like Google maps are included in websites).

Is this impact limited to Google only?

probably not. We can expect Yahoo to release a web API and jump onto the mashup train. This new branding channel is too good to be left to a competitor…

This architecture will¬†probably¬†be most useful when provided by other “independent” widget frameworks such as (mentioned in Reuters news). ¬†although this one does not yet provide a desktop engine for running its widgets and then is limiting their use to online mashup pages only.


this technology is not yet advanced enough for commercial use but will probably be added to the Ajax-web2.0 pot soon (1-2 years?) so it might be interesting¬†to keep an open eye on its progress…

We can also expect to see other widget engines to come up as well as there might be¬†a dormant commercial market for it and current vendors provide solution targeting more personnal sites than commercial sites. Such a vendor would benefit from the technology awareness provided by Google and heat it up by real applications…

Web cars

June 11, 2006

When web technology goes on wheels… A friend of mine told me about car hiring/sharing system. Seems pretty cool.. The idea is to rent cars by the hour when we need it, throught the web. Cars are located almost everywhere in large cities and we apaarently are able to find a car near our place at any time.

It seems to be cheaper that owning a car and also environment friendly..

The system is working in the US ( and also here in London (

See article: