Anybody know why this is? I use two CSS and a javascript wrapped in HTML.
http://cwf-wrestling.com
http://cwf-wrestling.com
My site works perfectly in IE, but not in FireFox
The same problem occurred to me.
But, with just minor adjustments in the alignment and design of my page, I have got it to work perfectly on both
It even works on opera or avant
But, with just minor adjustments in the alignment and design of my page, I have got it to work perfectly on both
It even works on opera or avant
Different web browsers have different degrees of CSS support, especially for CSS2. The following web page lists the various CSS properties and their support in some of the popular web browsers.
http://www.jessett.com/web_sites/css/css_browser_support.shtml
http://www.jessett.com/web_sites/css/css_browser_support.shtml
I've got firefox and your page works!!
Works pretty good in Opera too. This is techncaly spam, so I will add a bit. You should try to get some other browsers or find some friends with other browsers (mainly IE, FireFox, Opera, and Netscape) and then edit it a bit at a time and ensure that is still looks good.
Well thats why 90% of america still uses IE.
Sorry javascripts and layers do not work well in mozilla.
Mozilla= less pop ups and more functionality and limited java and html scripting
IE = All html works
Sorry javascripts and layers do not work well in mozilla.
Mozilla= less pop ups and more functionality and limited java and html scripting
IE = All html works
| DeFwh wrote: |
|
IE = All html works |
Well all html works... which isn't neccesarily a good thing, one of the reasons it has security flaws...
shucks i didnt realize that with spybot teatimer at all
Seriously if you use any os or any program most have security flaws.
How do any of us manage to survive the WWW.
Its terrifying now that WWW doesnt fit on a floppy anymore.
Seriously if you use any os or any program most have security flaws.
How do any of us manage to survive the WWW.
Its terrifying now that WWW doesnt fit on a floppy anymore.
Without your saying the difference between "working" and "not working" in this case, it is difficult to tell if your site is working under Firefox or not. I just tried it, and it appears fine, but if there is something that should be there that I am missing, I can't tell, since nothing was specified.
One thing I've among different browsers: even though some browsers have features that others don't, a lot of problems can be traced to different implementations of the same (or similar) features. In addition, the syntax may be different. For example: to use the document.anchors array under IE, one must enclose the subscripts in parentheses. Firefox, on the other hand, is more consistent in its syntax, and uses square brackets, as one would expect for array subscripts. Thus, it is necessary to have the code check for browser type (navigator.appName) then use
for IE and
for Firefox (and Opera).
One thing I've among different browsers: even though some browsers have features that others don't, a lot of problems can be traced to different implementations of the same (or similar) features. In addition, the syntax may be different. For example: to use the document.anchors array under IE, one must enclose the subscripts in parentheses. Firefox, on the other hand, is more consistent in its syntax, and uses square brackets, as one would expect for array subscripts. Thus, it is necessary to have the code check for browser type (navigator.appName) then use
| Code: |
| document.anchors(..... |
| Code: |
| document.anchors[.... |
| DeFwh wrote: |
| Sorry javascripts and layers do not work well in mozilla. |
Poopy head.
I've always told people who ask me this type of question this:
IE will forgive junk coding, and still show your page nicely, or at least, how you want it to be shown. I don't know how many times I've seen unclosed tags go by unnoticed by IE. This can be a good or bad thing, depending on your angle.
Now, Firefox and Opera are the same as one another, but different than IE. They'll pretty much spit out excatly what they're given - whether it be correct or not. If you're code is wrong, it'll show up in their window.
Few key good steps to basic web-dev:
1) Check different platforms. I have windows and linux installed just so I can view my sites on those platforms. Then, I have a mac box for checking it there too.
2) Check with every major browser out there for each platform.
3) Check with different resolutions. 800x600, 1024x768 and so on and so forth. If you have an ideal resolution (I usually shoot for 1024x768 myself) then make that apparent ("Best viewed at..."). But also make sure your site is still easily viewable and easy to navigate at other resolutions.
4) Have friends check it out on their computers. Hey, everyone has different settings. Don't just ask "Does this look OK to you?", instead, have them shoot off a screen shoot to you, so you can directly compare how they're seeing it to how you want it to be seen.
5) Lastly, test it off site before putting it up for the world. This might mean having your old site up for an extra day or something, but it just might prove worth it.
That's about all I can say... goodluck!
-Ray
IE will forgive junk coding, and still show your page nicely, or at least, how you want it to be shown. I don't know how many times I've seen unclosed tags go by unnoticed by IE. This can be a good or bad thing, depending on your angle.
Now, Firefox and Opera are the same as one another, but different than IE. They'll pretty much spit out excatly what they're given - whether it be correct or not. If you're code is wrong, it'll show up in their window.
Few key good steps to basic web-dev:
1) Check different platforms. I have windows and linux installed just so I can view my sites on those platforms. Then, I have a mac box for checking it there too.
2) Check with every major browser out there for each platform.
3) Check with different resolutions. 800x600, 1024x768 and so on and so forth. If you have an ideal resolution (I usually shoot for 1024x768 myself) then make that apparent ("Best viewed at..."). But also make sure your site is still easily viewable and easy to navigate at other resolutions.
4) Have friends check it out on their computers. Hey, everyone has different settings. Don't just ask "Does this look OK to you?", instead, have them shoot off a screen shoot to you, so you can directly compare how they're seeing it to how you want it to be seen.
5) Lastly, test it off site before putting it up for the world. This might mean having your old site up for an extra day or something, but it just might prove worth it.
That's about all I can say... goodluck!
-Ray
mm yes this has happened to me before when i was making my site... it was because of the tables i was using.
coding html+css with errors (which present ie versions can omit) is a stupid idea
remember, as ms announces, ie7 will be very close to w3c standards, closer than any previous version, and almost close as mozilla is.
your pages tested in ie 6 can became piece of s..it next year;-)
always code CSS for FF browser, then conditionally add IE hacks in separate stylesheet, eg.
(add this after linking to main css)
remember, as ms announces, ie7 will be very close to w3c standards, closer than any previous version, and almost close as mozilla is.
your pages tested in ie 6 can became piece of s..it next year;-)
always code CSS for FF browser, then conditionally add IE hacks in separate stylesheet, eg.
| Code: |
|
<!--[if IE 6]> <link rel='stylesheet' href='styles_ie6.css' type='text/css'> <![endif]--> |
(add this after linking to main css)
its probably in the HTML if its alignment problems, just use a div align tag and hey presto!
 |