Dear Jason:

On Thu, Apr 30, 2009 at 6:33 AM, Jason Simanek <> wrote:

> On Wed, 2009-04-29 at 11:50 -0700, Rob Healey wrote: It isn't that I
> do not care, but I can't program to make everyone happy!  If it were a
> mainstream browser, then I would say yes, but isn't any longer or is
> it???  I know that Internet Explorer is giant in the computing world,
> but is IE6?

Unfortunately IE6 is about as 'mainstream' as it gets. The numbers vary,
but IE6 can, depending on the site, still be more widely used than
Firefox. IE7 can only be installed on Windows systems running Windows XP
Service Pack 2 or higher. There are a lot of people running earlier
versions of Windows and even more that run XP without any updates.
However, Internet Explorer 7 use is starting to increase.

You have to keep in mind that 'not mainstream' is any Linux user. ;D

Now, I'm all for not bothering to correct small glitches that occur in
IE6. But we should be monitoring our web output on IE6 and other
browsers so that we know what the glitches are. There's been a lot of
development growth in the web reports in the last 12 months. Because of
that I think we need to go through a period of making our web output
work as consistently as possible. Validating test output with the W3C
validator is a great way to find some bugs, but in my experience valid
XHTML and CSS is not necessarily a guarantee that the pages render as
they should.

I'm even starting to notice some big rendering problems in Firefox 2
that thankfully don't exist in Firefox 3. In my eagerness to use Firefox
3 I failed to test on FF2, which is probably still more widely used than

Test, test and test again... I'm sure programmer's have a similar
experience, but this is definitely the life of a web designer/developer.

Have a great day,
Is it that much of an issue to have the <?xml ....> line in the output???   I guess it would truly depend upon what standards or line of validation that we choose to use?  W3C shows it as a standard part of their template, but some browsers are slow in getting caught up with the W3C...

So what should we do?  It would be easy to remove it, but how fast will it be before the browsers get caught up?  Should we downgrade a standard to please the browsers or should we leave it, and force the browsers to get on the ball?


Jason Simanek

Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3.
Gramps-devel mailing list