Re: [csswg-drafts] [css-scoping] Inclusive vs exclusive lower boundary (#6577)

So the options we currently have are:

1. `@scope (.a) to (.b)` vs. `@scope (.a) until (.b)
2. `@scope (.a) to (.b) inclusive` vs. `@scope (.a) to (.b) exclusive`
3. `@scope (.a) to inclusive (.b)` vs. `@scope (.a) to exclusive (.b)`

Leaving aside the question of which should be the default in 2. and 3., here's my thoughts on each of them:

1. For myself I'd choose this one, as it's shortest and saves unnecessary typing, but "to" and "until" are often used interchangeably in casual language so this may also be the most confusing.
2. This one is definitely easier to remember as the words have very clear definitions, but I can't find any specific advantage to putting these keywords at the end.
3. I slightly lean towards this one because it makes the keyword a bit more visible when reading the rule.

-----

In the case of 2. and 3., the question of which should be the default when neither keyword is used could be decided at a later moment. That way the question could already be narrowed down a lot.

-- 
GitHub Notification of comment by DarkWiiPlayer
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6577#issuecomment-1021035991 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 25 January 2022 10:27:24 UTC