On needing a timetable for CSS dash extensions

It was fun to be interviewed by a Northerner, not that shandy drinking Southerner Boag, and Ryan's choice of topic gave me the opportunity for me to dust off my soap box once again. The segment of the interview that so far has got the most attention was when Ryan asked:

Okay, well IE8 is also missing a few of the other more popular CSS3 selectors that are available in other browsers, like border-radius and things like that. Is this a setback for CSS3?

Here's what I said in response.

The interesting thing, though, and this is the wider issue, is that there’s no strategic plan, either from the browser makers or, most importantly, from the CSS working group, where they plan in a timetable implementation of these new features. Now we’re not talking about the big design of CSS, and when are we going to get new layout features and things like that, but simple things like for example CSS columns? Webkit implements CSS columns, Mozilla implements CSS columns, but they do it independently, they do it when they want to on their own timetable, and what I’d really like to see is for these browser makers to get together and say “You know what in September, we’re going to introduce these columns across the board, and in October, or in our next release, we’re going to implement this across the board.”

Today, Mozilla's David Baron replied. He wrote.

I agree that this would be really useful. The CSS Working Group actually went through a prioritization exercise last year. […] But this exercise had two problems as far as being useful for satisfying the goals Andy set out above.

First, all the feedback was secret (emphasis mine): it was provided only to the chairs of the group, who then computed the results, rather than allowing discussion and negotiation. I think this makes it harder for people to accept the results that they don't agree with. […]

So, given the results of the CSS working group prioritization, I don't know which things that I didn't consider important were marked as more important because other Web browsers want to implement them (which might mean I should increase the priority even though I don't like them, as I did for multiple background layers), and which were marked as important because of the preferences of companies whose priorities Mozilla shouldn't care about coordinating with.

I'd love to have a forum for discussing this prioritization with other browser makers so that our work can be used by Web authors sooner and more reliably, and I think it would be better if it weren't in a pay-to-play environment like the W3C.

Wow.