I agree to an extent. But, the webkit prefix situation is not the same as the IE problem. During IE's heyday, sites were tailored specifically to that browser

I agree to an extent. But, the webkit prefix situation is not the same as the IE problem. During IE's heyday, sites were tailored specifically to that browser, but due to IP and technical lock-in, other browsers were unable to implement the IE-specific features. (See ActiveX). Here, the problem isn't one of capability. The other browsers can (and have indicated that they will) implement the webkit syntax and feature set. The W3C is simply clinging to a failed spec "because its the spec". As was made clear in the OP's plea, the W3C needs browsers to observe their specs to remain relevant and avoid circumvention. If the webkit extensions aren't technically or legally barred from implementation, there's no reason that other browsers shouldn't simply adapt. Aside from the W3C's own self-interest, the only "problem" here is that the market is dictating the solution, instead of a panel of self-professed governors.