One day, Neil Crosby wanted to shadow some text using CSS. "So, the challenge was simple. Come up with some CSS which will produce drop shadows in as large a percentage of peoples’ web browsers as possible, leaving the browsers which are incapable of showing text shadows with unstyled text. Sounds simple? Well, for the most part, it was…
There are already tutorials out on the web which tell you how to produce text-shadows for various web browsers. The problem is, they all seem to focus on one particular browser, rather than producing a cross
Imagine this: overnight, the W3C makes CSS3 a standard, and the browsers end their differences (IE included) and support everything in CSS3. How will this affect you? What magical things that CSS3 offers will bring your webpages to life?
For instance, CSS3 gives us cross–browser opacity, standardized Image Replacement (via display: icon), and automatic box and text shadows, not to mention being able to control the resizing of a window through CSS. And there’s a lot more where that came from.
But then you wake up and realize that complete
HTML validation and CSS validation are controversial issues with some people. This article discusses some of the issues that have come increasingly to the fore in web development. The article will also provide a practical method that overworked webmasters can use to improve their website.
What does Validating HTML or CSS Mean?
For those who are unfamiliar with what validating a web page means, it basically refers to using a program or an online service to check that the web page that you created is free of errors. In particular, an HTML validator
Introduction
If you are a web designer or front-end developer, you are probably familiar with how different browsers or user agents displays your code in their own way. Picture this: You are pushing pixels and refining your designs so it fits perfect in your Firefox browser, but when presenting your design to the client in Internet Explorer, your pages might brake completely. Bye bye contract. Designing with CSS is no exception. On the contrary – table based layout seems to be more cross-browser consistent than CSS positioning. This probably one of
For those who are unfamiliar with what validating a web page (ie validating your HTML or CSS code) means, it basically refers to using a program or an online service to check that the web page that you created is free of errors.
In particular, an HTML validator checks to make sure the HTML code on your web page complies with the standards set by the W3 Consortium (the organisation that issues the HTML standards). There are various types of validators - some check only for errors, others also make suggestions about your code, telling you when a
Those who are against a blanket rule about validation often cite the following reasons:
1.
Validation is No Guarantee that Page Works
Even if you validate your code, you still have to test it in the various browsers. Having code with no syntax errors does not mean that the HTML or CSS code does what you want. Hence some of the proponents of this view argue that the main goal when designing a web page is to make sure it is viewable and usable by your visitors, not some esoteric goal of standards compliance.
2.
Time Constraint for
For some, the process of validation gets in the way as they create web content. That's a fairly dangerous attitude.
Integrate validation into your creative process. Once that becomes part of the way you do things, you'll thank me for it. As I like to say, "Validate early and often."
There are three real good reasons why you want to validate your work. Each of them support the principle of adherence to specifications.
1. It Helps Resolve Cross-Browser, Cross-Platform And Future Compatibility Issues
By creating files that are syntactically
RSS/XML