When a feature like developer.mozilla.org/en-US/… is implemented across multiple engines, I expect the spec for it to be in somewhat decent shape.
2
2
I don't expect to find multiple fundamental missing pieces just skimming the spec. First 3 implementors should have reported those.
2
2
But it's css-multicol, so I just filed github.com/w3c/csswg-drafts/… #1072 is worst, #1071 is also bad, & somebody should have noticed the rest.
1
1
I do recall suggesting that maybe column-span should be punted to level 2 of this spec. Now I regret not pushing harder on that.
2
Also, when people propose moving specs to CR, I need to ask: "Who other than the editor can say they read it and it looks ready?"

Mar 4, 2017 · 12:15 AM UTC

1
2
Replying to @davidbaron
Find myself begging ppl to read the spec so I can send it to CR with some amount of confidence, and the WG is like <silence/>.
1
1
Maybe better to target one person (but not the same one each time) than to have diffuse responsibility?