[css-contain-3] Nesting Context (side effect / enhancement)

Based on the current implementation in Chrome Canary and Safari TP Container Queries seems to only need a property name – allowing them to be used to expose nesting context.

  /* this works */
  .container-a {
    container-name: A;
    container-type: inline-size;
  }

  @container A (inline-size) {
    .child { color: orange; }
  }

IMO it makes a lot of sense to use Container Queries to handle this scenario (child styling without a direct reference to the container selector(s)).

If possible it would be nice if container-name could be used without having to specify container-type and query

  /* simplified syntax (suggestion) */
  .container-a {
    container-name: A;
  }

  @container A {
    .child { color: orange; }
  }

Codepen Example

I hope it makes sense and that I haven't overlooked existing issues
Thank you for your hard work – it is highly appreciated
😃

Start with the issue's container-name and @container examples and compare them with the current CSS Containment Level 3 draft and the linked CodePen. Determine whether property-only container names and a query without a condition should be supported; done requires a resolved specification direction and corresponding draft changes.