Web standards

W3C, WASP, A List Apart, Open Web, OpenSource, Evolt, WSG, QuirksMode, W3QC, Accessify

Unobtrusive JavaScript

June 30, 2008 Posted by

As a designer, you can’t just hope that your active JavaScript is functioning well – some people disable scripts by default, because they put a heavy load on their Internet connection. This makes sense because loading a larger script can severely delay the loading of a single page. This is the reason why you should think of an unobtrusive JavaScript when you are designing a website.
You can meet people, however, who don’t see the need for such an approach. In the end, it is much easier to assume that all users support JavaScript, and this effort for a small group of Internet users is just a waste of time. Fortunately, the number of people who see an unobtrusive JavaScript as something more than a slogan. For those who don’t much on this issue, I suggest a few points to consider when designing a website:

  1. Avoid erroneous assumptions – it is worthwhile to test your site with JavaScript disabled, and if something is not working properly, it’s the result of the erroneous assumption that all users have the JavaScript enabled in their browsers;
  2. You have to design your HTML code logically – both before or during the coding you should preplan all possible interactions between HTML and JavaScript;
  3. Avoid bloated scripts – you want to use CSS, where possible; using JavaScript is slower and often unnecessary, especially if it is just about the visual aspect of an element;
  4. You must understand both browsers and users – It is worth examining whether the huge opportunities offered by JavaScript match the capabilities of the popular browsers as well as the needs of users; it so often happens that fancy interfaces with JavaScript disabled fail;
  5. It is necessary to understand the nature of events – you want to dig into the JavaScript documentation in order to learn the event handling, which will allow you to separate the script from HTML;
  6. You should avoid conflicts – it is worth examining whether the use of two different libraries / scripts will not cause errors in the entire service; it’s good to optimize the existing code;
  7. It is necessary to take into account the future of the service – you want to write scripts, so that the next encoder or developer does not have a problem with the existing coments and annotations.

RDFa in XHTML: Syntax and Processing

June 20, 2008 Posted by

The Semantic Web Deployment Working Group and XHTML2 Working Group have published a Candidate Recommendation of RDFa in XHTML: Syntax and Processing. RDFa is a specification for attributes that express structured data, which are used with HTML and XHTML . W3C invites implementations (see RDFa implementation report).

New Firefox Version 3.0

June 17, 2008 Posted by

On 17 June 2008, Mozilla released the fourth major version of Firefox browser. According to the developer, there are more than 15,000 improvements in the newest release, including less memory requirements, a smart location bar, the ability to zoom in on a portion of a Web page, an integrated tool to manage add-ons , and improved security.

Mozilla has set up a Firefox-3 download counter to see if the company can break the world’s record in the most downloads. You can also see how many people all over the world download Firefox every minute.

You can download the browser by clicking the image below.

firefox download

CSS3-which way to go

June 6, 2008 Posted by

Many people feel that the first version of CSS was a breakthrough – it’s hard to disagree with that. CSS2 was received somewhat less enthusiastically – a lot of people were pointing to the fact that there was no clear vision for the further development of this standard. Time flies quickly, and 10 years after the birth of CSS1 a new version (CSS3) is looming in the horizon. There are a lot of voices of support and criticism (which is prevailing). When cruising the blogosphere, I found at a very interesting article on the evolution of CSS – (strongly critical).
The article is written by Alex Russell, who believes that such important issues as inheritance and variable replacement should have been already implemented in CSS 2. It turns out that you can’t find these either in the CSS 3 draft. Instead, the people working on the development of CSS focus on less ambitious goals. The fact is that, at the moment, the question of inheritance is highly neglected, although CSS is somehow handling this issue. Sometimes, you want to import one uniquely “named” class (previously defined) into another. Unfortunately, such a mixing is disallowed, and you have to hardcode the values, which unnecessarily inflate the entire code.