Today I got the last edition of T3N and there was an article about Web standards and how different browser manufacturers try to extend the functionality using proprietary solutions to compensate a bad functionality of CSS 2.1. Web developers and browser manufacturers waiting for a long time for the publication of CSS3 standard. The problem is that the rapid development of Web prepares more and more new tasks for Web developers and browser manufacturers. The websites and the kind of the creation of Web sites is becoming increasingly complex and requires new ways. These possibilites that we have today are not enough any more. CSS3 could be a solution to the problem of growing demands. However, no one knows when CSS3 finally will be published. For this reason, most of browser manufacturers began to introduce of their own CSS properties, which should help the developers to create modern websites.
But the problem is that the browser market is no longer dominated by one browser. The proportions between multiple browsers are divided. While Microsoft Internet Explorer has remained the majority, the other browsers were able to win a big slices of this pie in the last time.
But if the Web developers would begin now to use proprietary properties, then they would create a chaos. The pages, depending on the browser would have a different look. The effort in creating a Web site would rise rapidly.
I am of the opinion that the responsibility for this development is on the developers of CSS standard. In my opinion, this consortium should be restructured so that its efficiency would be higher. The development of standards at this time don’t really work. I understand that Web is still relatively young and all of these childhood diseases would be someday solved. But now I see no real effort by various sides, to solve the core of these problems.
Archive for the ‘CSS’ Category
CSS standards and who bears responsibility for browser incompatibilities
Monday, November 17th, 2008Video-tag in HTML
Wednesday, October 15th, 2008Since the publication of HTML 4.01, HTML standard was not changed. Many developers declared HTML dead and switched to XHTML. I am also not an exception, because I switched from HTML to XHTML Transitional, then to Strict and later completely to XHTML 1.1. Mostly I develop web pages based on TYPO3 and use many plug-ins. I have a lot of work in the adaptation of templates so that they generate a proper code. The reason is, different developers of the plugins are using different technoligy.
Today, I learned via Golem.de that Mozilla integraded into Firefox 3.1 a video-tag. Moreover, according to Golem, Opera and Safari made it too. This means that you can soon use video-tag instead of Flash or Silverlight. It also means that HTML is not dead, because video-tag ist a part of the HTML 5.0 specification.
It’s just so that when you are the developer, you have to lern every day something new. If you stop for some time, to lern new technologies, then you have bad cards, if you would like to stay in business for a long time. But why must it be so complicated? Why should I use parallel HTML and XHTML? Would it not make sense, to develop an once technology constantly, instead to develop multiple specifications? I could understand the situation if there was no organization which control the developing of standards. But this organisation exists! I would prefer to continue using XTML, instead of HTML 5, because there will be a chaos, between developers, who works on the same project, e.g. TYPO3.
Google doctype: What do you want to know today?
Sunday, May 25th, 2008
Doctype Google is the new ambitious project by Google. It is an attempt to create a free technical encyclopedia for CSS, HTML and DOM. It consists of not only from the articles, it has also the code of the encyclopedia freely accessible. As in the Google video presentation the saying goes, “Google doctype is an encyclopaedia, by the developers and for the developers”.
Although there are a few articles and HowTo’s there, I am sure that Google can find many motivated supporters which will constantly fill the encyclopedia with new knowledge. Anyone who has a google account can participate.
Whether Google Doctype could be a competitor to selfhtml.org? At the moment it is still difficult to say, but the themes are very close to each other. It is important that selfhtml is only in the German language very detailed. The English version and also those in other languages, are less complete.
Therefore, I can say that Google Doctype could not be described as comptetitor for selfhtml.org, it is a device to close the knowledge gap. Previously you had to browse through various sources to find an answer for your question, today, thanks to projects such as Google and Wikipedia, the knowledge in consolidated in a few sources. This saves time and time is money.
css stuff
Tuesday, July 17th, 2007Today I have found an interesting web resource with css tutorials. You can reach it at
http://css.maxdesign.com.au/index.htm
An interesting method to make graphic gradients
Friday, June 15th, 2007Matthew O’Neil wrote an article about a possibility to make gradients with different
colours and only one graphic file.
This method doesn’t work in IE6, but because IE7 will be released by Microsoft on the next time as security update for all windows users, I hope that IE6 will lose a priority.
http://alistapart.com/articles/supereasyblendys
HowTo: Center of the elements
Monday, April 9th, 2007Center of an element is very simply, but many beginners have problems with it. I was asked about it many times and I would like to present you a little HowTo:
<body style=”text-align:center;”>
<div style=”position:absolute; top:50%; margin-top:-50px; height:50px;
left:50%; width:100px; margin-left:-50px;” >
<div style=”position:absolute; text-align:center;”>
<div style=”height:100px; width:100px; background:red;”></div>
</div>
</div>
Attention: the value of margin-top should be a 50% of height-value and value of margin-left = 50% of with.
Bulletproof Webdesign (Dan Cederholm)
Monday, February 19th, 2007Bulletproof Webdesign is one of the best books about css that I ever read. The author was able to explain the most important rules of bulletproof webdesign in one book.
Each article of the book has a example of methods and an explanation why it is bad and how you can make it better.
I would suggest Bulletproof Webdesign for all, who are interested in learning of modern methods of web design.