Skip to content

Commit d0230a2

Browse files
committed
[css-anchor-position] Remove issue, Elika agrees only scroll/contain clipping should apply
1 parent 9092136 commit d0230a2

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

css-anchor-position-1/Overview.bs

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1091,10 +1091,6 @@ where this could be the case.
10911091
or being clipped to its [=overflow clip edge=]
10921092
(such as by ''overflow: clip'' or [=paint containment=]).
10931093

1094-
Issue: Should any other clipping matter?
1095-
The 'clip'/'clip-path'/'mask' properties?
1096-
''opacity: 0''?
1097-
10981094
Note: This means that if an abspos is next to its anchor in the DOM,
10991095
for example,
11001096
it'll remain visible even if its default anchor is scrolled off,
@@ -1113,16 +1109,6 @@ where this could be the case.
11131109
(due to its anchor being scrolled off),
11141110
then another abspos using it as an anchor will also be hidden,
11151111
rather than <em>also</em> floating in a nonsensical location.
1116-
1117-
Issue: I think we don't want to make this dependent
1118-
on any <em>other</em> types of invisibility.
1119-
Anchoring an ''opacity: 0'' element
1120-
might make sense, for example.
1121-
This property's hiding is based on dynamic state,
1122-
which you can't otherwise select on;
1123-
all of those other sources are caused by other styling,
1124-
which you can just condition this element on as well
1125-
if you want to hide it at the same time.
11261112
</div>
11271113

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

0 commit comments

Comments
 (0)