Previously in alt.html, "...D." <d@no_usenet_email..org> said:
> Is this microsoft purposely doing this or what is it?
Pretty much. They make up whatever they like and call it HTML.
> It is a simple HTML code used: <bgsound src="hasta.mp3" />
Except that a) That's not HTML. The <bgsound> element does not appear in
any published version of HTML.
b) It's XHTML syntax, even if the <bgsound> element did exist.
c) It's a bad idea, anyway.
> Of course I know in several cases Firefox and netscape have special needs
> in coding for scripts.
You mean they need you to do it properly?
> No darn wonder firefox is so security resistent - it cannot do half of the
> stuff it should..
Like what?
> Firefox - conform, dammit!!.
It conforms a lot closer to any of the standards than IE does.
> even just placing a
> day/date/month javascript on a page and firefox displays a line lower down
> than IE. does. Same with the slideshow. even with the whole added script
> just for it, it still displays the slide show window lower down on the
> page than I.E,.
If Firefox displays a page differently to IE, chances are it's IE that's
wrong. Generally it means that your code is written badly, and IE just
happens to guess what you want. Firefox on the other hand, actually does
what you tell it to. If you don't like it, you need to fix your code.
> crap firefox... what a hassle..
Let me make a suggestion.
Forget IE. Use Firefox as your primary testing browser. Write your code.
Include a doctype that triggers "Standards Mode" in all browsers.
Validate your (X)HTML and CSS. Once you have it working correctly in
Firefox, and it all validates, test it in Opera (chances are it will
work fine). Then test in other browsers (Konqueror, Safari, older
versions of all of the above, etc.), adding hacks if necessary, then
testing in Firefox and Opera to make sure hacks haven't caused any
problems in them. Then, and only then, test in IE, and add any hacks you
need to so that IE will display it correctly. Once that is done, test in
all the other browsers again to make sure the hacks haven't broken
anything in them.
Once you have done the above, you can think about adding optional
extras, such as Javascript. Again, test in Firefox, then Opera, then
other browsers, and finally IE. As long as you write your Javascript
according to the published specifications, IE should have no problems if
it works in the other browsers.
--
Mark Parnell
http://www.clarkecomputers.com.au
|
|
