At the introduction of CSS, two main browsers on the market, Microsoft’s Internet Explorer 4 and Netscape 4 did not fully support it. Netscape did horribly broke the entire standard, while IE came closer to it but with some important bugs. So, the developers had to create a different version of CSS for every browser, in order to be sure that their pages would render correctly on every one of them.
In time, when the standards became more important, the developers had to choose whether to create the next version of browser closer to the W3C
A cool find by Aaron Gustafson from Webstandards.org, here his post: In a fairly interesting move, Amazon is now allowing aStores to be customized using CSS.
This morning, Amazon announced that their aStore product (part of the selling tools available to folks enrolled in the Amazon Associates program) would allow full customization of the look and feel via CSS. Currently, the interface only allows for approximately 8000 characters of custom CSS, but that level of control is allowed on several of the page types, including product descriptions and
It seems like the eternal question amongst web developers: HTML or XHTML? Wherever I look there seems to be posts in forums raising the question, web developers asking me or other people write blog posts about what they believe is the right way to go. I’m not writing this post to tell you what the ultimate choice is, but rather to inform you about the consequences of what you choose. So, let’s take it from the top:
Strict or Transitional?
Definitely strict. Transitional doctypes are exactly what the name implies: a doctype for a phase of
This is a well-discussed and very important topic. Personally, presently I write XHTML for my web interface code, but lately I’ve started to stagger in my standpoint. For normal general web page design, what’s the gain? If you don’t extend the code with namespaces, use MathML, have your own DTDs and so on, why would you want to use XHTML?
Many people answer that question with: “It makes me write leaner code, code that has to validate and be more semantic correct”. Martin 0 wrote a post 0 recently why he uses XHTML (unfortunately, it’s in
This is a well-discussed and very important topic. Personally, presently I write XHTML for my web interface code, but lately I’ve started to stagger in my standpoint. For normal general web page design, what’s the gain? If you don’t extend the code with namespaces, use MathML, have your own DTDs and so on, why would you want to use XHTML?
Many people answer that question with: “It makes me write leaner code, code that has to validate and be more semantic correct”. Martin 0 wrote a post 0 recently why he uses XHTML (unfortunately, it’s in
It seems like the eternal question amongst web developers: HTML or XHTML? Wherever I look there seems to be posts in forums raising the question, web developers asking me or other people write blog posts about what they believe is the right way to go. I’m not writing this post to tell you what the ultimate choice is, but rather to inform you about the consequences of what you choose. So, let’s take it from the top:
Strict or Transitional?
Definitely strict. Transitional doctypes are exactly what the name implies: a doctype for a phase of
The discussion of XHTML versus HTML has popped up again, and until now I've managed to resist the urge to throw in my 2¢. Well, no longer will I sit on the side line while the same arguments get rehashed again and again, which will not get us anywhere. In this article, which I originally published in my blog, I'll attempt to answer this question: does the future of the Internet lie with HTML or XHTML?
Firstly, I'm just going to set a few ground rules. This is not going to be another version of XHTML as text/html is considered harmful or there are no
RSS/XML