IIS Sending IE and FF different code, an ASP fix?
-
Is there a away to force IE and Firefox to get the same HTML when they attempt to access my pages? IE gets correctly formatted HTML and FF get's messed up HTML. I know the HTML itself is different, (Yay windif) and I've proven that the IE source works fine in FF and the FF is still broken in IE. Any help with this would be great. It hinders my project a great deal. And it kinda sucks to have to be telling our customer that he is having to use a browser we've advised him not to use in the past. The wisest of the wise may err. - Aeschylus Codito Ergo Sum - (I code, therefor I am)
-
Is there a away to force IE and Firefox to get the same HTML when they attempt to access my pages? IE gets correctly formatted HTML and FF get's messed up HTML. I know the HTML itself is different, (Yay windif) and I've proven that the IE source works fine in FF and the FF is still broken in IE. Any help with this would be great. It hinders my project a great deal. And it kinda sucks to have to be telling our customer that he is having to use a browser we've advised him not to use in the past. The wisest of the wise may err. - Aeschylus Codito Ergo Sum - (I code, therefor I am)
It's your own fault for recommending Firefox over IE. You should stay out of religious discussions like that, especially if you want to give bad advice. Let your users tell you what browsers to support, it makes life easier if it's only IE, and it will NEVER be only Firefox. If it's an ASP.NET site, then ASP.NET could be trying to generate correct HTML based on it's browser detection. If this is screwing up, try to work out which control is generating the wrong HTML and try to figure out why. Christian Graus - Microsoft MVP - C++
-
It's your own fault for recommending Firefox over IE. You should stay out of religious discussions like that, especially if you want to give bad advice. Let your users tell you what browsers to support, it makes life easier if it's only IE, and it will NEVER be only Firefox. If it's an ASP.NET site, then ASP.NET could be trying to generate correct HTML based on it's browser detection. If this is screwing up, try to work out which control is generating the wrong HTML and try to figure out why. Christian Graus - Microsoft MVP - C++
I do know what pages are sending the poorly formatted HTML, and I can't figure out why. It's just labels and text boxes and standard controls that get shifted so they overlap. So I'm not sure what control would be causing it. Is there a good resource I can use to learn how IIS is detecting different browsers and perhaps modify the detection to result in sending same/similar HTML as it does for IE. Note - I didn't recommend Firefox, I recommened not IE. :) The wisest of the wise may err. - Aeschylus
-
I do know what pages are sending the poorly formatted HTML, and I can't figure out why. It's just labels and text boxes and standard controls that get shifted so they overlap. So I'm not sure what control would be causing it. Is there a good resource I can use to learn how IIS is detecting different browsers and perhaps modify the detection to result in sending same/similar HTML as it does for IE. Note - I didn't recommend Firefox, I recommened not IE. :) The wisest of the wise may err. - Aeschylus
Baatezu wrote: It's just labels and text boxes and standard controls that get shifted so they overlap. So I'm not sure what control would be causing it. You're sure it's not because of problems with Firefox CSS ? We actually employ someone to make sure we have HTML that Firefox can cope with. Baatezu wrote: Note - I didn't recommend Firefox, I recommened not IE. Isn't that the same thing ? It's certainly bad enough, IMO. Christian Graus - Microsoft MVP - C++
-
Baatezu wrote: It's just labels and text boxes and standard controls that get shifted so they overlap. So I'm not sure what control would be causing it. You're sure it's not because of problems with Firefox CSS ? We actually employ someone to make sure we have HTML that Firefox can cope with. Baatezu wrote: Note - I didn't recommend Firefox, I recommened not IE. Isn't that the same thing ? It's certainly bad enough, IMO. Christian Graus - Microsoft MVP - C++
Would a problem in FF's CSS change the HTML the 'View Source' options shows, or is the server sending different code? If I save the source from IE and load it in FF it looks right, and FF's source is still messed up when loaded into IE. I would disagree that recommending a browser other than IE is the same as recomending FF. Opera, iRider, Mozilla (yea same engine) are all also available for use. I'm sure there are more. The wisest of the wise may err. - Aeschylus
-
Would a problem in FF's CSS change the HTML the 'View Source' options shows, or is the server sending different code? If I save the source from IE and load it in FF it looks right, and FF's source is still messed up when loaded into IE. I would disagree that recommending a browser other than IE is the same as recomending FF. Opera, iRider, Mozilla (yea same engine) are all also available for use. I'm sure there are more. The wisest of the wise may err. - Aeschylus
Baatezu wrote: Would a problem in FF's CSS change the HTML the 'View Source' options shows, or is the server sending different code? If I save the source from IE and load it in FF it looks right, and FF's source is still messed up when loaded into IE. Yeah, I noticed you'd said that, which makes it seem unlikely, but I can't imagine what else could be going on here. We support Firefox, and we've never had this problem. Baatezu wrote: I would disagree that recommending a browser other than IE is the same as recomending FF. Come on now, which other browser has the publicity that FF has ? Either way, you've pushed yourself into a corner. Why on earth recommend not IE ? Like I said, IE is what most people use, and what ASP.NET is bound to support best. If you want FF, why not go J2EE ? Christian Graus - Microsoft MVP - C++
-
Baatezu wrote: Would a problem in FF's CSS change the HTML the 'View Source' options shows, or is the server sending different code? If I save the source from IE and load it in FF it looks right, and FF's source is still messed up when loaded into IE. Yeah, I noticed you'd said that, which makes it seem unlikely, but I can't imagine what else could be going on here. We support Firefox, and we've never had this problem. Baatezu wrote: I would disagree that recommending a browser other than IE is the same as recomending FF. Come on now, which other browser has the publicity that FF has ? Either way, you've pushed yourself into a corner. Why on earth recommend not IE ? Like I said, IE is what most people use, and what ASP.NET is bound to support best. If you want FF, why not go J2EE ? Christian Graus - Microsoft MVP - C++