Skip to content

Commit bed3a61

Browse files
committed
[css-anchor-position] Make strongly-hidden elements also trigger hiding of things depending on them. w3c#7758
1 parent c4626dd commit bed3a61

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

css-anchor-position-1/Overview.bs

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1091,6 +1091,26 @@ where this could be the case.
10911091
Issue: Make sure this definition of clipped
10921092
is consistent with View Transitions,
10931093
which wants a similar concept.
1094+
1095+
|anchor| is also considered [=clipped by intervening elements=]
1096+
if it is [=strongly hidden=]
1097+
by 'position-visibility'.
1098+
1099+
Note: This ensures that in a "chained anchor" situation,
1100+
if the first abspos is hidden due to this property
1101+
(due to its anchor being scrolled off),
1102+
then another abspos using it as an anchor will also be hidden,
1103+
rather than <em>also</em> floating in a nonsensical location.
1104+
1105+
Issue: I think we don't want to make this dependent
1106+
on any <em>other</em> types of invisibility.
1107+
Anchoring an ''opacity: 0'' element
1108+
might make sense, for example.
1109+
This property's hiding is based on dynamic state,
1110+
which you can't otherwise select on;
1111+
all of those other sources are caused by other styling,
1112+
which you can just condition this element on as well
1113+
if you want to hide it at the same time.
10941114
</div>
10951115

10961116
Making an element <dfn noexport>strongly hidden</dfn>

0 commit comments

Comments
 (0)