.Net and IE7

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

There was a post in the general newsgroups that I have also run into, see
below.

I have a .Net 2.0 application that runs fine and displays fine in IE6, but
the asp:Panels and asp:GridViews overlap each other and look like a mess.

Screen prints are at http://www.criminonwus.org/IE7.doc

Please advise.

Thanks.




Subject: Re: IE7 & ASP.net another BUG 8/29/2006 5:55 PM PST

By: Sam Brown In: microsoft.public.internetexplorer.general


I've also had problems in rendering the ASP.NET 2.0 wizard control.
 
IE7 is much better at rendering the page correctly than IE6 is. If there
is a difference in apperance, it's very likely that it is rendered
correctly in IE7, not in IE6.

Also test the page in a browser like Firefox or Netscape. They are much
better at rendering pages correctly. In most cases you will find that
they look about the same in IE7 and Firefox/Netcape.

Here you can read about bugs in different browsers:
http://www.positioniseverything.net/

In the section "Explorer Exposed!" you will find the long list of
rendering bugs in IE6. That can be compared to the list of rendering
bugs for Firefox/Netscape in "Open Source Oopsies" that consists of only
two, which both are fixed.
 
Thanks.

Did you look at the screen prints that I sent to you?

If IE7 is rendering it correctly then there is a bug in .Net on how it is
sending the data to the page as grids and panels shouldn't be overlapping.

I can force the height of the grid in code, and it then displays correctly
in IE7, but that seems like a clunky solution.

This whole page is coded in version 2 of .Net, with no HTML errors noted
even using the highest validation type.

Why would IE6 show it correctly, and IE7 make it look like garbage?

Thanks.
 
Gerhard said:
Did you look at the screen prints that I sent to you?

If IE7 is rendering it correctly then there is a bug in .Net on how it is
sending the data to the page as grids and panels shouldn't be overlapping.
Click to expand...

Not necessarily. Just because the data isn't correct doesn't mean
there's a bug in .NET.
I can force the height of the grid in code, and it then displays correctly
in IE7, but that seems like a clunky solution.

This whole page is coded in version 2 of .Net, with no HTML errors noted
even using the highest validation type.

Why would IE6 show it correctly, and IE7 make it look like garbage?
Click to expand...

You seem to have defined "correctly" as "the way I want it to" rather
than "the way the HTML standards say it should".

Out of interest, how does it look on Firefox and Opera?

Without seeing any HTML, it's impossible to say what's going on with
any certainty. However, you can easily take .NET itself out of the
equation: save the HTML page and look at it carefully. Reduce it to the
simplest possible HTML that demonstrates the problem, and then if that
doesn't help to explain what's going on, post that minimal HTML in an
HTML newsgroup.
 
Additionally, the likelyhood of it being a difference in how IE 6 and IE 7
interpret CSS instructions is strong. HTML 4.01 has been standardized sing
1998 (3 years before IE 6), but CSS took a bit longer to be fully
implemented by browsers and standardized.
 
Gerhard said:
Thanks.

Did you look at the screen prints that I sent to you?
Click to expand...

No, I didn't. I don't have Office installed at the moment. I know how a
web page built specifically for IE6 can look like in a standards
compliant browser, though. I've seen it many times.
If IE7 is rendering it correctly then there is a bug in .Net on how it is
sending the data to the page as grids and panels shouldn't be overlapping.
Click to expand...

That depends on the layout. Elements can very well be made to overlap,
and if you rely on the rendering bugs in IE6 to position the elements,
they will surely render differently in a browser that is lacking those bugs.
I can force the height of the grid in code, and it then displays correctly
in IE7, but that seems like a clunky solution.

This whole page is coded in version 2 of .Net, with no HTML errors noted
even using the highest validation type.
Click to expand...

There is a big gap between correct markup and working markup. Just
because the markup doesn't contain errors, doesn't mean that it's good,
or even that it makes sense.
Why would IE6 show it correctly, and IE7 make it look like garbage?
Click to expand...

Most likely the correct rendering of your markup looks like garbage (no
critisism intended), but in IE6 the bugs makes it render it differently
so that it looks like you want it to look.

Many seems to believe that IE6 constitues the standard, just because
it's the most used browser, while it's rather the opposite. The real
standards, however, are the standards that the World Wide Web Consortium
(W3C) has developed, of which Microsoft is one of the over 400 members.
 
From what I'm hearing, it sounds like this issue is related to the way that
IE6 handles CSS margins and padding, which is incorrect, according to the
current standards. IE7 corrects these 2 issues and renders CSS padding and
margins according to standard. That is what I would look at first.

--
HTH,

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

What You Seek Is What You Get
 
Kevin said:
From what I'm hearing, it sounds like this issue is related to the way that
IE6 handles CSS margins and padding, which is incorrect, according to the
current standards. IE7 corrects these 2 issues and renders CSS padding and
margins according to standard. That is what I would look at first.
Click to expand...

Perhaps you are talking about the box model bug that IE6 suffers from in
quirks mode, where it handles padding and borders incorreclty. IE7
renders the page exaclty the same in quirks mode as IE6 does (for
compatibility reasons), so IE7 will not correct that.

What IE7 does correct is all (?) the bugs that IE6 has in standards
compliant mode.
 
Back
Top