[success story] Standard compliance strikes back


Recommended Posts

Are you a firebird user? I know I am. And I'm absolutely sick and tired of incorrect coding on websites that "looks fine" in IE, while it's quite clearly coded improperly, when viewed in Firebird.

One such instance of this was on one of my favorite websites, where "Which font the site used" was absolutely imparative.

Here is evidence that there is still hope for we, the firebirders, and proof that a little email can fix alot.

Hello Lee,

Thanks for bug report and a such detailed how-to instruction.

We will fox that ASAP.

Actually, we're getting such reports starting this month.

I've looked into html source and I see from where it comes.

It's really weird that I have not recognized the problem from the very beginning.

Thanks again!

---------------------------------

Best regards,

Eugeny Naidenov

webmaster@ultimate-guitar.com

http://www.Ultimate-Guitar.Com

---------------------------------

--- Saturday, November 22, 2003, 1:12:39 AM, you wrote: ---

wuu> To whom it may concern-

wuu>            Hello, I'm an avid reader of your site, and webmaster

wuu> of my own (work in progress), and I thought that I might notify you

wuu> of a (rather

wuu> large) error in the coding of your site. Here's the long and short

wuu> of it-

wuu>            => The short: Tablature is not properly spaced in some browsers.

wuu>            => The long: For starters, Internet Explorer is a

wuu> poorly coded browser. I'd like to make my position clear that I

wuu> think very highly of your site, and of the code behind it. Any

wuu> "errors" in your code are not your own fault; they are the fault of Internet Explorer displaying the "wrong code"

wuu> in the "right fashion". I'll be referencing Mozilla Firebird 0.7

wuu> (http://www.mozilla.org/products/firebird/) throughout this email-

wuu> It is the most "standards-compliant" web browser available, and if

wuu> it works in Firebird, it was coded perfectly- Plain and straight.

wuu>            That being said, the problem lies in line 30 of

wuu> "/img/css.css", as well as in a few other lines in the same file

wuu> (Reference classes "TD" and "Menu"). These lines are written

wuu> perfectly- They are set to use the Verdana font for all operations

wuu> on the site. However, when Internet Explorer parses these lines, it

wuu> cannot correctly read the code, and it defaults to the font Courier, instead.

wuu>            The true problem lies deeper in. Guitar Tablature is,

wuu> quite obviously, very dependent on the fact that all characters are

wuu> the same space apart. For example, let's use a bigger scale of

wuu> measurement, and pretend that every "dash" ( - ) is 3 meters long.

wuu> If the tab consists of multiple strings (as most do), it is

wuu> absolutely imperative that every character above the "dash", and

wuu> every character below it, be exactly 3 meters long. And in most

wuu> fonts, it will be- or at least close. However, in the Verdana font

wuu> (displayed by Standards Compliant browsers, because your code is

wuu> properly written), letters ("h", "p" and "b" are commonly used) and

wuu> slashes (such as /, often used to indicate a slide) are not this

wuu> exact length. They vary. So in an average line with, say, 10 "dashes", if the line below it contains these non-uniformed characters, the line will not be exactly 30 meters long.

wuu> Since the timing of a strum is relative to it's location on the

wuu> dashed line, this causes a large problem. If you do not understand,

wuu> compare the introduction to Jimmy Olsens Blues by the Spin Doctors

wuu> (or any other complex

wuu> song) between the two browsers.

wuu>            The error comes directly from the fact that you're code

wuu> is good, and the Internet Explorer error makes the page display in

wuu> Courier - what's known as a "Fixed Width" font - which is a good

wuu> thing. So during the coding of the page, everything looked correct

wuu> when tested. However, once put in a browser that displays it as it

wuu> was coded, the font is replaced by Verdana, and the alignment is lost.

wuu>            The simple solution would be to go into "/img/css.css"

wuu> and replace the word "Verdana" with "courier" in every instance. IE

wuu> users should not notice much of a change, but it may fix the page

wuu> for those who prefer a more Standards Compliant browser.

wuu> I thank you for your time.

wuu> Sincerely,

wuu>            Lee Bailey, webmaster of Uplinked.us

I don't know why I'm putting this here, but I feel that it serves as an example for every FB user that's ever seen a page and just switched to IE.

Don't put up with errored coding. It's not hard to get the webmasters to change it, they're usually very receptive.

We'll win this fight for a better internet... or something like that.

Link to comment
Share on other sites

our company has a mandatory checklist for all developers. part of html developers checklist is required compatability with at least IE6 and Mozilla browers. optionally, if clients agrees, we'll also make sure everything looks fine in IE5.5/IE5.0/Win9x/Opera :)

however some developers are very ignorant and refuse to spend any time fixing thier "correct" MSHTML errors :pinch: since their weblogs show that 70% of visitors use IE :no:

Link to comment
Share on other sites

All you have to use is Opera, if it displays every bit of code in Opera, it will work in any browser. I am glad to see that complaining gets something done. Being an Opera & Firebird user, I have sent many emails with no replies. Thanks for sharing.:)

Link to comment
Share on other sites

All you have to use is Opera, if it displays every bit of code in Opera, it will work in any browser. I am glad to see that complaining gets something done. Being an Opera & Firebird user, I have sent many emails with no replies. Thanks for sharing.:)

When I tried Opera, I always got errors, and pages that did not show up correctly. I got tired of it and went back to IE.

Link to comment
Share on other sites

I meant when writing or designing a page to be fully standards compliant, view it with Opera, if all the coding shows up and everything works as it should, it will work in any browser.You got errors because the page was written only for IE, and designers too lazy to do the work so that anyone coming across their site,regardless of browser choice, would have an enjoyable experience, and not get error messages.

:)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.