"HTML/CSS" Correctness
I have noticed allot of other networks including Collectivex, Not having "valid" HTML or CSS coding within their pages.. I remember the "W3C Validation" service site and decided to run the validation on just one "A" typical page or network.. The network was unaltered with only limited entries.
On average, the page returned 56 errors and 34 warnings.. Just wondering.. and I have been told by "other" networks.. and I quote: "As long as it works, we do not plan to alter or correct the settings". Sorry I asked.. Thou I am a bit of a stickler when it comes to just a few things pertaining to html and css coding, Mind you I am not an excerpt and I have some limited or basic skills when it comes to this. However for some reason.. When (in the past) I used Blogger.com and uploaded my own template and ran the same W3C Validation test.. I received less errors and I was able to correct them accordingly.
Knowing this.. I'm sure many out there would say, "IF it works, etc.." leave it alone. But i tend to like the little "Validation" badge posted on all of my pages, Knowing the page is valid and I was able to make these corrections with any help.. Granted it probably took me many months to complete.. but I did it.
If there isn't any issue with HTML and CSS correctness, Why is there a standard for HTML or CSS.. or is this just a personal thing.. and no one follows the rules anymore. One thing is for sure.. because I and many of you know some of these codes, many of us do not not care to. They simple want to log onto a site and not have to deal with the many issue that they could face down the road.
For instance, If my page or network has been tested and another user joins without the experience of making the necessary corrections to his or her page.. and they enter an "In-Valid" code or information, thus my network is invalid as well.. So seems I'm going in circles.
So, is it pointless to even have a "standard" or correctness to ones page?.. We goto school for a reason.. to learn.. but I just feel that people today whom write these codes and formats are not taking the time to truly gain the benefit of the schooling they where taught. By the way, even correctness can have errors..
Just an observation.
| Topic | Replies | Likes | Views | Participants | Last Reply |
|---|---|---|---|---|---|
| Subgroup Initials & Resorting | 2 | 0 | 100 | ||
| Email Blasts | 3 | 0 | 102 | ||
| Filing Cabinet Default location | 1 | 0 | 101 |
Wizard,
I am actually very interested in following standards. Unfortunately, the browsers are not - and they force us to break standards in order to have a usable page. I remember back at the beginning of this decade when I realized the impact that these new features had on development - and I shuddered at the fact that browsers now foisted this upon developers.
Until w3c adds autocomplete as a valid HTML attribute, our pages will not validate. We will not stop using autocomplete because browsers then can freely ignore form values - which quickly turns from a mere annoyance into an utter disaster when you combine this issue with JavaScript that expects the page to be in a certain state to run. I'm sorry but it simply takes way too much development time to workaround browser insanity in JavaScript when a single attribute assignment fixes it in all browsers.
If you have a markup-only alternative to using autocomplete="off" I'm all ears. My only requirement is that it has to work. And in all browsers.