W3C home > Mailing lists > Public > www-validator@w3.org > June 2008

Re: Missing attribute in a <script> element (Was: Re: [VE][127] Add Subject Here)

From: Sierk Bornemann <sierkb@gmx.de>
Date: Fri, 13 Jun 2008 13:05:49 +0200
To: Jukka K. Korpela <jkorpela@cs.tut.fi>
Message-Id: <1C0A7CDC-A7D9-48EE-920D-97FF6BCA51AD@gmx.de>
Cc: www-validator Community <www-validator@w3.org>

Hi Jukka!

Am 13.06.2008 um 11:59 schrieb Jukka K. Korpela:
>
> Even IE 7 does not recognize them.


Maybe a test like Acid4 or Acid5 on http://acidtests.org/ may be able  
to force Microsoft to dive into it and change that. :-)
Acid2 seemed to be a good way of motivation to force the IE team to  
achieve better particular standards support.
I have discussed with Ian Hickson several times to take a short test  
into Acid3, which tests the support for these per RFC4329 recommended  
mimetypes, but Ian denied, lastly because of the pre2004-limitation of  
the tests, and RFC4329 has been published 2006.
Concerning the data: URI scheme, which also is defined per RFC and  
tested by ACID3, I have been encouraged to propose a RFC4329-test for  
the recent Acid-Test.
Because Microsoft seems to take the Acid-Tests now more serious than  
ever any standards body and testsuite before, I am encouraged to hope  
for better times. :-)
Concerning Open-Source projects like Firefox, Konqueror/WebKit and  
Apache, everybody is able to make some little pressure and discuss and  
ask and help out with patches. But concerning a closed source project  
like the Internet Explorer, other ways of making pressure to change a  
state must be found. Or does the Internet Explorer Dev Team have a  
wide open Bugtracking portal, which is open for proposals and  
particular suggestions? I haven't found one. The other browser makers  
do have such a bugtracking system/portal.
I think, the popular Acid tests seem to be a viable possibility to  
take the IE team into action concerning such needs.
Another possibility would be the market itself -- the highest pressure  
group you can imagine and maybe the only *actual* language, Microsoft  
understands: if their product doesn't make it, if it fails some  
particular standards all other competing products are able to fulfill,  
then this Microsoft product has a big problem: the customer/consumer  
has the power and the right to choose and to use another product  
instead, which fulfills the needs.
The spiral and problematic situation will never end, if the developers  
and consumers always take regard of Microsofts products and their  
problems they have in fulfilling general standards and/or  
webstandards. The free capitalistic market is powerd by choice. And  
the customer/consumer indeed *has* choice. Why hiding this choice to  
guard a particular product? Why not foster the choice in using and  
promoting standards, all other rivals of Internet Explorer are capable  
of or are better capable of? I am the opinion, considering the weaks  
and problems of Internet Explorer too long, consolidates the status  
quo and only delays a solution, because there is no pressure for  
Microsoft to change something and to make their products better.

Twiddling one's thumbs and waiting and hoping for a day, Microsoft  
might move anything sometime, doesn't change anything. Not now, not in  
the future. The problem would only be stretched into an undefined  
future, if you do nothing and only refer to the status quo and wait.
So, only actually *using* the standards on a *wide* base (and not!  
avoiding them) and force them and promote them and make tests suites  
like the Acid-Tests so popular that they are mandatory for the browser  
makers -- especially for Microsoft -- only then you have the chance to  
change something.

Sierk
-- 
Sierk Bornemann
email:            sierkb@gmx.de
WWW:              http://sierkbornemann.de/
Received on Friday, 13 June 2008 11:06:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:29 GMT