Skip to content

[css-cascade-6] Fix link errors, etc #8467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 17, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
[css-cascade-6] Fix link errors, etc
  • Loading branch information
andruud committed Feb 17, 2023
commit bc14a7267bb93fb73ef484b4114f6dedbd3a3b83
5 changes: 3 additions & 2 deletions css-cascade-6/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ spec:css-values-3; type: value; text:ex
spec:css-conditional-3; type:at-rule; text:@media
spec:mediaqueries-4; type:type; for:@media; text:all
spec:mediaqueries-4; type:type; text:<media-query>
spec:selectors-4; type:dfn; text:subject
</pre>

<pre class=ignored-specs>
Expand Down Expand Up @@ -377,7 +378,7 @@ Scoping Styles: the ''@scope'' rule</h4>

[=Pseudo-elements=] cannot be [=scoping roots=] or [=scoping limits=];
they are invalid both within <<scope-start>> and <<scope-end>>.

A ''@scope'' rule which does not specify a <<scope-start>>
produces a single <dfn>implicit scope</dfn> as follows:

Expand Down Expand Up @@ -529,7 +530,7 @@ Scoped Descendant Combinator</h4>
This combinator differs from the [=descendant combinator=]
in that it applies [=weak scoping proximity=]
to the relationship between <css>A</css> and <css>B</css>.
It does not change the [=:scope element=].
It does not change the '':scope'' element.

ISSUE: Should the [=scoped descendant combinator=]
use strong or weak scoping proximity?
Expand Down