- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Jun 2021 19:02:24 +0000
- To: public-css-archive@w3.org
mirisuzanne has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain-3] Bikeshed the container property & at-rule names to avoid confusion with other usage of contain/container == In the [CSS Containment Module L3](https://drafts.csswg.org/css-contain-3/) we define [`container-type`](https://drafts.csswg.org/css-contain-3/#container-type), and [`container-name`](https://drafts.csswg.org/css-contain-3/#container-name) properties, along with a [`container` shorthand](https://drafts.csswg.org/css-contain-3/#container-shorthand). I personally think "container" is the clearest term we have for this feature (and [twitter seems to agree](https://twitter.com/TerribleMia/status/1395440175128342528), but there is some potential for confusion. We already have a (related but different) `contain` property, and many other variations pm "container" terminology in CSS specifications. Other names that have been suggested: - `query` (clear association, but the verb doesn't entirely make sense when applied to the containing element) - `context` - `component` - `module` - `structure` - `viewbox` - `enclosure` - `compartment` Unfortunately, many of these alternative also have existing meaning that could cause confusion. (Depending on the language we choose, `@container` may also need to be updated.) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6376 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 June 2021 19:03:14 UTC