On Tue, 2009-10-06 at 15:55 -0400, Ken MacDonald wrote:
> FYI, I don't think I mentioned it before, but this problem occurs in
> both the build and source versions of the application.
>
> Something else interesting - I got a brand-new laptop when I started
> here in August. Came with Windows XP - SP3. And IE 6. I'd have thought
> a new computer would come with a more recent version of IE.
Ha-ha, Ken. That's sort of funny! New computer, but old operating
system. The current XP SP3 OEM install is the original SP3 release from
some years ago, and the OEM versions are a fixed-point in time - they
don't get updated over time. Consider yourself lucky that you could
still get XP - ooo, that's a politically-loaded statement. Sorry.
IE6 has been the XP-bundled browser since the beginning; I believe XP's
SP3 update was even before IE7 came out, despite the fact that MS is
already on IE8 now. As I remember reading in a recent search for IE6
workarounds, it took Microsoft quite a few years to replace IE6 with IE7
(like 7+ years), which is surprising due to how bad IE6 behaves. I
guess the browser wasn't a priority for MS until Firefox started to kick
their butts in that area a few years ago.
Your browser version is not a surprise at all to me, and I keep it
around on my XP laptop so that I can test sites on IE6 to make sure
normal stuff is going to work correctly for all those XP users out there
in the world. Getting IE6 to work in most areas just required me to
spend a great deal of time reading MSDN documentation, which is fairly
comprehensive once you find the details on their site. You have to know
which object parameters are implemented in IE6 and which are not, in
addition to figuring out how to use parameters that are not implemented
correctly.
I did find one trick to getting IE6 to behave better: transmit a
standards header prior to the opening HTML tag to get the browser to
render in standards-compliant mode. I assume Qooxdoo takes care of
these types of details, but it's helpful to understand these little
quirks (a missing standards header triggers the *quirks* display mode)
to avoid surprises in your page rendering. Quirks mode means the
browser actually displays in the previous IE version's rendering mode
rather than the newer IE6 rendering methods. They did this so older
websites that didn't send the standards header would display the same as
before in older IE versions, but a lot of developers never picked up on
the fact that IE6 and later versions work better if you specify a
standards header to trigger the newer display modes.
Sorry that was so long, but your comment triggered a need to share my
new-found knowledge with the list - I hope it helps somebody out there.
Gene
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
