Firefox
Posted: Wed Nov 30, 2005 11:52 am
Anybody know any html bugs that will make a page hideously horrible in firefox but normal in ie?
A community of PHP developers offering assistance, advice, discussion, and friendship.
http://forums.devnetwork.net/
It depends on your definition of "A page". Seriously.The Ninja Space Goat wrote:Anybody know any html bugs that will make a page hideously horrible in firefox but normal in ie?
[/quote]The Ninja Space Goat wrote:I'm sorry I should have elaborated a bit...
I want to make a site that comes up perfect in IE, but fails miserably in firefox because I would like to prove a point to somebody, so if anybody knows ways to do that... let me know.
My boss won't let me use firefox because he can't spy on me when it is open... I am a webdesigner. I need to be able to test sites in all browsers. I could wait a month for complaints to roll in that sites aren't coming out right in firefox, or I could just show him now. I haven't searched long and hard. I asked one question at one site. I hate IE I want to use firefox. Don't look for negative in everything. Just answer the damn question or don't post in my thread.sweatje wrote: So... the point your making is that if you search long and hard enough it just might be possible to find a page that renders worse under FireFox?![]()
Perhaps try googling for "this page best viewed in IE"... pages, surly there are some that are malformed enough to suit your needs
I just want to be clear that being trained in debate, I can always take the other side in an argument. As a result, if you want a page that doesnt work in FF, you want non-standard code.The Ninja Space Goat wrote:I'm sorry I should have elaborated a bit...
I want to make a site that comes up perfect in IE, but fails miserably in firefox because I would like to prove a point to somebody, so if anybody knows ways to do that... let me know.
HUH!?! If you want to use Firefox, you'd want to show the opposite of what you are asking for - that Firefox renders things correctly, while IE *doesnt*.The Ninja Space Goat wrote:My boss won't let me use firefox because he can't spy on me when it is open... I am a webdesigner. I need to be able to test sites in all browsers. I could wait a month for complaints to roll in that sites aren't coming out right in firefox, or I could just show him now. I haven't searched long and hard. I asked one question at one site. I hate IE I want to use firefox. Don't look for negative in everything. Just answer the damn question or don't post in my thread.
I see what you are saying, but my point is not that FF is better, but that if I can't use FF, I can't test sites in FF. If I made sites that render fine in IE, but not in FF, customers who use FF will have bad experiences with our websites. This is inevitable since I cannot test sites in ff, and do not always use complient code.Roja wrote:HUH!?! If you want to use Firefox, you'd want to show the opposite of what you are asking for - that Firefox renders things correctly, while IE *doesnt*.The Ninja Space Goat wrote:My boss won't let me use firefox because he can't spy on me when it is open... I am a webdesigner. I need to be able to test sites in all browsers. I could wait a month for complaints to roll in that sites aren't coming out right in firefox, or I could just show him now. I haven't searched long and hard. I asked one question at one site. I hate IE I want to use firefox. Don't look for negative in everything. Just answer the damn question or don't post in my thread.
I think your attempt would prove why you should use IE, not FF.
AH. Interesting approach. Now I see the logic. I don't quite agree thats the best way to convince the boss, but I'm not in your shoes. Good luck!The Ninja Space Goat wrote:I see what you are saying, but my point is not that FF is better, but that if I can't use FF, I can't test sites in FF. If I made sites that render fine in IE, but not in FF, customers who use FF will have bad experiences with our websites.
No reason not to. If you always use compliant code, you'd have far fewer problems. Not to mention, if you are doing it for work, the pages *probably* need to be accessible, so they need to be compliant.The Ninja Space Goat wrote:This is inevitable since I cannot test sites in ff, and do not always use complient code.
Well I am moving towards that... it is a goal of mine, but complient code takes time, and time isn't something I have since my boss thinks a website should take 2 hours as it is.Roja wrote:AH. Interesting approach. Now I see the logic. I don't quite agree thats the best way to convince the boss, but I'm not in your shoes. Good luck!The Ninja Space Goat wrote:I see what you are saying, but my point is not that FF is better, but that if I can't use FF, I can't test sites in FF. If I made sites that render fine in IE, but not in FF, customers who use FF will have bad experiences with our websites.
No reason not to. If you always use compliant code, you'd have far fewer problems. Not to mention, if you are doing it for work, the pages *probably* need to be accessible, so they need to be compliant.The Ninja Space Goat wrote:This is inevitable since I cannot test sites in ff, and do not always use complient code.
(*nitpicker note: Accessibility doesn't require html compliance. However, most of the items it requires are easily accomplished by creating compliant code.)
This is tricky for me to answer, because I can't claim I code in non-compliant code, and spend the time converting it. I don't. I always develop html-compliant code.The Ninja Space Goat wrote:Well I am moving towards that... it is a goal of mine, but complient code takes time, and time isn't something I have since my boss thinks a website should take 2 hours as it is.
What would be your approach to changing his mind on this? Keep in mind he has no idea what he is talking about when it comes to web design. He thinks FrontPage is good.