Skip to content

Commit 163d240

Browse files
committed
docs(ios): say plainly how a text view indicator clipped the list
1 parent 5c82b1c commit 163d240

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

  • packages/capture-kit/src/ios-snapshot-engine

‎packages/capture-kit/src/ios-snapshot-engine/scroll.ts‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -60,11 +60,11 @@ function collectIosScrollIndicatorNodePresentation(
6060
/**
6161
* The scroll container an indicator reports on. XCTest publishes a UIScrollView's indicators as
6262
* children of that view, so the nearest scroll-typed ancestor is normally the owner. A UITextView
63-
* is a UIScrollView too but publishes as `TextView`, and its indicators sit inside the text: read
64-
* onto the list around it, they clip that list to one line of text and drop every row after it
65-
* (a post thread whose root post is selectable text lost all of its replies). An indicator whose
66-
* nearest scrolling ancestor is a text view belongs to that text view, which derives no viewport,
67-
* so it resolves no container.
63+
* is a UIScrollView too but publishes as `TextView`, and its indicators sit inside the text. When
64+
* such an indicator was treated as the surrounding list's, the list's viewport shrank to that one
65+
* line of text and every row after it was clipped away (a post thread whose root post is
66+
* selectable text lost all of its replies). An indicator whose nearest scrolling ancestor is a
67+
* text view belongs to that text view, which derives no viewport, so it resolves no container.
6868
*/
6969
function findScrollIndicatorContainer(
7070
node: RawSnapshotNode,

0 commit comments

Comments
 (0)