Jump to content

Possiable Error/mud slinging


Guest BuzzLightYear_AL

Recommended Posts

Guest BuzzLightYear_AL

First off let me say that this site has been invaluable to me and my work. I use it on a daily basis.My co-workers sometime are hesitant to use it, don't know why, but some are.Well first the possible error, On page http://www.w3schools.com/tags/tag_img.asp there is a paragraph stating:---------------------------------------------Mozilla Firefox and the alt AttributeIf you use the alt attribute in Firefox on images and image maps the text will not show on mouse-over as in other browsers.Firefox uses the alt attribute the way it's meant to be used, like an alternative text if the image won't load, not as a mouse-over text.Firefox does support mouse-over comments on images or image maps if you use a title attribute in the <img> tag.E.g. <img src="image.gif" alt="bla" title="bla bla bla"---------------------------------------------First the E.g. is a incomplete tag.....Second.... IE, or at least IE 7 and maybe others, not sure as to I am not investigating all versions, the statement .... "Firefox uses the alt attribute the way it's meant to be used" is a biased statement against Microsoft's IE, which is totally unprofessional and discouraging to new programmers. It is also incorrect statement implying that IE does not Display the "alt" text on an image. IE works just as "the way it's meant to be used", the "alt" text shows in place of the image when the image is unavailable.There will always be differences between all browsers, and the argument has gone on forever, but that doesn't mean that in a professional environment we should take "sides" because it really depends on your point of view. I once had a problem with Netscape in 2 areas, on was using references to low level intrinsic functions, such as "var Print = document.writeln", and I also had a problem with "onclick" firing off on a <a> tag. I actually had a phone conference with the development team. After several of these calls, they had found the problem, which was in the very low level core of x-path, (I think that was the name), and basically told my company that they wasn't going to fix the bug, and yes they called it a bug, because it was so entrenched in the core. Don't even get me started with the differences of "position" when used between IE and Firefox. One positions "absolute" by the container holding the object, and the other is positioned by the containing element ONLY if it had is positions set, otherwise it transverses up the object tree to the first element that does set its position or the document itself if no containing object didn't set a position. I had to experiment and observe this myself to figure it out completely after I saw a reference to it on another site because w3schools had no information on this, at least not on this page, http://www.w3schools.com/css/pr_class_position.asp. Now which one "correctly" handles this? Well that depends, if it is by container, then the one that varies is incorrect, if it is by Document then they both are wrong. My observations may be incorrect, however this statement shows no biases towards either browser because I haven't stated which one is which. However I could make this statement using indications as to how each works OR I could use some mud-slinging statements like "Browser 'blank' is so incorrect because it doesn't support a constiant operation when it should only represent it in this form and not a varying format" or "This 'blank' browser supports positioning as it was meant to be used."My point is, avoid any biased comments as it destroys the confidence we have in using your site for solid information. And yes I have seen other like statements elsewhere on the site. I not asking for you to be perfect and you shouldn't expect others to be perfect either.Well thats my 2 cents worth, I realy do just love your site and I hope to continue to use it. It is a fantistic resource for the Web.!!!!BuzzlightYear

Link to comment
Share on other sites

"Firefox uses the alt attribute the way it's meant to be used" is a biased statement against Microsoft's IE, which is totally unprofessional and discouraging to new programmers. It is also incorrect statement implying that IE does not Display the "alt" text on an image. IE works just as "the way it's meant to be used", the "alt" text shows in place of the image when the image is unavailable.
I don't know.. if a browser uses something incorrectly, is it really biased to say that? I don't think that statement implies that IE does not display the alt text for a missing image. I think the statement is trying to point out the fact that the proper use of alt text is to be displayed when the image is not present, and since IE also shows the text on mouseover, it would be inappropriate to put text in the alt property and assume that it will be shown on mouseover, since that is not what the alt property is for.I'm not a new programmer, but I don't think saying things like this is discouraging for a new programmer. When I was starting out, I was discouraged by the fact that browsers did things differently, not by people pointing those differences out. It's important that new programmers realize that IE is not The Internet, and if you are making web pages that are only being tested in IE, then your pages are probably not going to work like you expect in other, more compliant browsers.Furthermore, since IE so poorly implements most standards, and encourages people to develop sites that only work in IE through things like ActiveX and VBScript, I think that, as a web programmer, a bias against it is completely appropriate.
Link to comment
Share on other sites

I was more discouraged as a programmer when my code didn't work in all browser than when I found out there was a difference between them. :)

Link to comment
Share on other sites

I was more discouraged as a programmer when my code didn't work in all browser than when I found out there was a difference between them. :)
Yeah, me too. I remember frantically going through my code, wondering if I'd done something wrong somewhere myself, like my coding had been ambiguous or something. It was a relief and at the same time a grief to learn of the huge browser differances.
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...