- From: Jon Rimmer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Apr 2020 20:57:20 +0000
- To: public-css-archive@w3.org
I don't understand this objection. Since the current spec already supports a two-value syntax, then can't people can already specify that combination? Unless it's illegal, in which case what difference would having separate properties for `display-inside` and `display-outside` make? Furthermore, given the whole web development industry, both standards-based (web components) and framework-based (React, Angular, Vue, etc.) has spent that last decade pursuing component-oriented development, why is a single problematic combination being allowed to prevent the delivery of a basic mechanism of layout encapsulation, the lack of which is a huge pain point? I'd really like to give people the benefit of the doubt here, but the dropping of `display-inside` and `display-outside` seems to point to a total disconnect between the reality of contemporary web development and what's happening in this part of the standards process. -- GitHub Notification of comment by jonrimmer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4729#issuecomment-607485936 using your GitHub account
Received on Wednesday, 1 April 2020 20:57:24 UTC