Opacity in Internet Explorer 8 development

Warning This article was written over six months ago, and may contain outdated information.

After just recent­ly writ­ing a post on CSS3.info which prais­es the CSS Work­ing Group for their inter­ac­tion with and com­mu­ni­ca­tion to the web devel­op­ment com­mu­ni­ty, now I have to write one cas­ti­gat­ing Microsoft for doing the opposite.

As for­mer Microsoft (and now Mozil­la) employ­ee Al Billings explains, the Inter­net Explor­er team went some way to mend­ing burnt bridges when they opened up their lines of com­mu­ni­ca­tion and engaged the com­mu­ni­ty dur­ing the devel­op­ment of IE7; most of that good work has been undone since then, how­ev­er, as they’ve gone more or less silent about new devel­op­ments on their blog since launch.

We have no idea what they are class­ing as impor­tant for their next release; no idea whether it’s worth invest­ing our time in SVG, Micro­for­mats, or any oth­er new stan­dard. I under­stand if they don’t want to release details of any new brows­er func­tions they might be work­ing on, but an occa­sion­al Alpha of the updat­ed Tri­dent engine would be more than welcome.

I don’t think it’s good enough that the mak­er of the brows­er with the largest mar­ket share should be keep­ing the peo­ple whose jobs depend on it in the dark. The con­ver­sa­tion with the com­mu­ni­ty should have con­tin­ued after the launch of IE7, and should be ongo­ing. As Al Billings summed up:

Engage­ment is not some­thing that you do for a year and then turn off for anoth­er year before repeat­ing. It is a reg­u­lar process of com­mu­ni­ca­tion and openness. 

More: Open­ness and IE, or “Talk to us!”; IE Team Silence.

6 comments on
“Opacity in Internet Explorer 8 development”

  1. I total­ly agree. It looks like it’s time for the IE team to come back down to earth.

    I real­ly get sick of the way they treat us.

  2. […] take is a strong dis­claimer that fea­tures were only exper­i­men­tal and not guar­an­teed for launch. As I said before, even if full Betas were not released, at least an Alpha or two of the lay­out engine with a basic […]

  3. […] com­plaints from the web com­mu­ni­ty about lack of trans­paren­cy in the devel­op­ment of the next Inter­net Explor­er, and a little […]

  4. This is a fuck­ing dis­grace imo

    Peter White [May 30th, 2008, 20:02]

  5. Thank god for at last Explor­er is final­ly giv­ing them hyp­ocrites some of their non­sense ““stan­dards”” back to their teeth. 

    This proves that every­thing con­tain­ing the (now final­ly) mean­ing­less word “stan­dard” is a hol­low pro­pa­gan­da that has nev­er had any­thing to do with true stan­dard­iza­tion of the brows­er mar­ket. W3C is a dis­grace to a moraly stand­ing soci­ety of the net for it has become a filthy weapon in the hands of browsers wag­ging war against a beau­ti­full and a high­ly capa­ble brows­er like Explor­er 4.01 which by the way stil after 11 years of age is more flex­i­bile and more com­pli­ant to the coders needs than W3C CSS3 will ever be.

    To hell with all hyp­ocrits and liars. Those who are yelling “stan­dards” can’t have and won’t have opac­i­ty sim­ply because it’s a NONSTANDARD fea­ture! This should be clear to every stan­dard hyp­ocrite. You have to decide to either sup­port “stan­dards” that are keep­ing inter­net in the era of Jura or to embrace the rev­o­lu­tion once start­ed back in 1997 by the only one true Brows­er: The Inter­net Explorer.


  6. I am one of the web­mas­ters that are ready to cry “foul” for the way IE8 pre­tend­ed to go for stan­dards com­pli­ance but then turned around and not only did­n’t sup­port CSS3 opac­i­ty prop­er­ties but added insult to injury with yet anoth­er opac­i­ty code abor­tion in IE8, to add to the already nasty IE 6 and IE7 abor­tions! Hypocrites!