|
|
Posted by Gιrard Talbot on 02/07/06 00:36
Stan McCann wrote :
> =?ISO-8859-15?Q?G=E9rard_Talbot?= <newsblahgroup@gtalbot.org> wrote in
> news:44pl8nF3b1guU1@uni-berlin.de:
>
>> Even if Microsoft would fix half of the documented, reported bugs
>> and implement just half of the missing, incomplete support for CSS2,
>> DOM 2, and other expressed/formulated specific requests in the final
>> release of MSIE 7, there would be major problems for web developers.
>>
>> 1- People do not automatically upgrade to the latest available
>> browser release. Adoption/migration of more recent browser release
>> versions is a slow process and takes years. Studies have shown that
>> a majority of people usually go ahead with a browser upgrade
>> along/at the same time with an operating system upgrade. So one
>> should expect to see MSIE 6 to represent a large chunk of the
>> browser market for the next 5 years or so.
>>
>> 2- Many windows users will not be able to upgrade to MSIE 7 anyways
>> since MSIE 7 will be possible only for XP users and Windows 2003
>> users. A considerable minority (20% - 30%) of the windows market
>> will not be using MSIE 7 anyway during the next few years.
>>
>> So, regarding web standards support and compliance in browser usage,
>> developers will have to deal with an overall fragmented browser
>> picture in the years to come. That's at best.
>>
>> Now the only remaining question is how well, good, complete, how
>> much will the MSIE 7 final release fix the utterly explained,
>> described, documented CSS/DOM bugs, unsupported DOM 2 attributes,
>> methods, unsupported CSS 2.1 properties? This beta 1 release is
>> sending the message; it suggests me that we should not expect more
>> than a 50% effort from Microsoft.
>>
>> So, speaking of patience means in my mind that things will be fixed
>> completely and for good with MSIE 8 ... around 2012.
>
> Ha! If then. Microsoft, IMO, is holding back innovation, despite
> their claim during the Netscape-IE "war" of several years ago when Bill
> was spouting off about including the browser in the OS being good for
> innovation.
>
> Firefox, and some of the other browsers on the market are our only hope
> of ever having a browser that fully implements standards.
I'd say Firefox, Opera, Safari, Icab are browsers trying to fully
implements standards. All of them achieved more in implementing support
for web standards than Microsoft and IE in the last 5 years.
I don't and
> can't, but I'd love to see web developers begin ignoring IE when
> developing.
In some cases, this can and should be done. position: fixed is one
example of this. Now that IE7 supports position:fixed and knowing that
position:fixed degrades as position: absolute in non-compliant browsers,
then it can be done.
When all of those IE users cannot get what they are after
> using a non-www browser, they'll switch to something that they can use
> to get what they want. I'd love to present IE users with blank pages
> like I so often get due to my non-use of js, cookies and plugins of all
> kinds. They'd switch, believe me. But getting all those companies
> with crappy sites to switch, well your 2012 estimate may be way too
> soon.
>
I'd prefer to see companies with crappy sites to upgrade entirely their
crappy sites: that's what I sincerly believe they should do.
"Browser makers are no longer the problem. The problem lies with
designers and developers chained to the browser-quirk-oriented markup of
the 1990s-often because they don't realize it is possible to support
current standards while accommodating old browsers."
http://webstandards.org/about/history/
GΓ©rard
--
remove blah to email me
[Back to original message]
|