Thanks for the sugestion Nareau, but I discounted that approach because the proportion of visitors wth JS dissabled is increasing all the time. This is likely to increase even further in the light of recent IIS hacking exploitations using JS to infect visitors.
This solution is excelent when it works, but when a visitor with a non JS browser visits, the wheels fall off.
In addition, a visitor with a NN4.x browser who turns off JS also efectively runs with no CSS. For me that is an awesome challenge.
This solution is excelent when it works, but when a visitor with a non JS browser visits, the wheels fall off.
In addition, a visitor with a NN4.x browser who turns off JS also efectively runs with no CSS. For me that is an awesome challenge.