On Monday 2018-06-25 13:18 -0700, Becca Hughes wrote: > >> On Fri, Jun 22, 2018 at 12:47 AM, Rune Lillesveen <futh...@chromium.org> > >> wrote: > >>> The CSSWG resolved on four values and edits to be made to CSS Variables > >>> Level 2[1]. Do we have a resolution overriding that to put it in a > >>> separate > >>> spec? > >>> > >>> I would not be comfortable shipping this without having these four > >>> values put in a spec with a description of what they are. > >>> > >> > >> I am not sure about the resolution, I will let @Tab answer that one. > >> > >> I added a pull request to add them to the spec: > >> https://github.com/w3c/csswg-drafts/pull/2807 > >> > > > It looks like Tab will be OOO for the next couple of weeks, but this > shouldn't block launch.
I think the underlying objection here is that we don't want to get in a situation where multiple implementations are shipping a feature that doesn't have a specification. I don't think that something being in Tab's backlog of specification editing in an acceptable resolution to that, given the size of his backlog. I also don't want to be in a situation where Tab is the single person gating new features; other people should be able to edit CSS specifications, particularly when given appropriate mentoring and advice. So I'd be substantially happier here if there were a specification before a second implementation shipped, but I also think getting that specification done shouldn't require any one particular person to be involved. -David -- π L. David Baron http://dbaron.org/ π π’ Mozilla https://www.mozilla.org/ π Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: PGP signature
_______________________________________________ dev-tech-layout mailing list dev-tech-layout@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-layout
