Hi Jerry,
Yep you are probably right about what's coming in the next IE, but may I
suggest that you are missing a point of web development.
It sounds like you are using FX as your browser for development? All good an
well, but how many of your users will be using FX?
Latest numbers suggest only 14%. It is counter intuitive to spend 80% of
your development time for a platform that will only work on 14% of your
users browsers. Add to that, that there are several versions of FX and IE to
contend with, and Safari seems to be the browser of choice for MAC
platforms.
Even if IE does become fully W3C compliant, there are still the legacy
versions to contend with. I will leave it to you to choose the browser of
choice for development, but for me the stats says it all. An important
consideration is that ALWAYS 'The User is King', colors, fonts and font
sizes should always be the choice of the user. What may look 'stunning' in
your development environment may not receive the same response from a user
(with different accessibility needs or browser platform).
Regards.
> Heya
>
[quoted text clipped - 32 lines]
>
> http://windowshelp.microsoft.com/communities/newsgroups/en-us/default.mspx?mid=d
316a6be-64e4-4522-b44c-4e82178f28e8&dg=microsoft.public.internetexplorer.general
C A Upsdell - 06 Feb 2008 22:20 GMT
> Hi Jerry,
>
[quoted text clipped - 8 lines]
> IE to contend with, and Safari seems to be the browser of choice for MAC
> platforms.
Speaking as a designer, it makes more sense to do the initial design for
standards compliant browsers like Firefox, and then to find out what
minor tweaks are needed by the various versions of IE to make the design
work well with IE.
The reason for this is that, in my experience, it takes less time to
start with valid code, and then to work out the IE tweaks, than it would
to start with badly broken IE-focused code, and then work out how to
make it work with standards compliant browsers.
Another issue is that designing to the standards avoids problems with
future versions of IE, which will be more standards compliant.
As to the Safari issue: it is quite standards compliant, and a site
that works well with Firefox and Opera typically works with Safari and
Konqueror with no changes. In my experience.