Skip to content

[11.0 P6] Docs for virtualize updates#37270

Open
ilonatommy wants to merge 2 commits into
mainfrom
virtualize-updates
Open

[11.0 P6] Docs for virtualize updates#37270
ilonatommy wants to merge 2 commits into
mainfrom
virtualize-updates

Conversation

@ilonatommy

@ilonatommy ilonatommy commented Jun 19, 2026

Copy link
Copy Markdown
Member

@ilonatommy ilonatommy self-assigned this Jun 19, 2026
@ilonatommy ilonatommy changed the title Docs for virtualize updats Docs for virtualize updatws Jun 19, 2026
@ilonatommy ilonatommy changed the title Docs for virtualize updatws Docs for virtualize updates Jun 19, 2026
@guardrex guardrex changed the title Docs for virtualize updates [11.0 P6] Docs for virtualize updates Jun 19, 2026
@ilonatommy ilonatommy marked this pull request as ready for review June 24, 2026 13:50
@ilonatommy ilonatommy requested a review from guardrex as a code owner June 24, 2026 13:50
@guardrex

Copy link
Copy Markdown
Collaborator

Hi @ilonatommy! ... I'll be back on July 1st. 🏖️

@guardrex guardrex left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with mostly NITs.

I think this is for .NET 11, right? I suggest a moniker range change.

Otherwise ...

  • I dropped in a few definite articles ("the"), which seem to make those sentences read a bit better.
  • I dropped in a couple XREF cross-links for API.

BTW ... If you want to, you can set the ms.date to the planned Pre6 release date of 07/14/2026.


:::moniker-end

:::moniker range=">= aspnetcore-10.0"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for .NET 11, correct? Also, I'll include my "UPDATE 11.0" tracking comment for getting the API into place after GA.

Suggested change
:::moniker range=">= aspnetcore-10.0"
:::moniker range=">= aspnetcore-11.0"
<!-- UPDATE 11.0 - API Browser cross-links -->


### `InitialItemIndex` parameter

Set `InitialItemIndex` to open the list at a specific item index on first interactive render. This is a one-shot parameter—changes after first render are ignored. Out-of-range values are clamped.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Set `InitialItemIndex` to open the list at a specific item index on first interactive render. This is a one-shot parameter—changes after first render are ignored. Out-of-range values are clamped.
Set `InitialItemIndex` to open the list at a specific item index on the first interactive render. This is a one-shot parameter—changes after first render are ignored. Out-of-range values are clamped.


### `ScrollToItemAsync` method

Call `ScrollToItemAsync` to programmatically scroll to an item after first render. The scroll is instant (no animation). The method returns a `Task` that completes when the target item is aligned to the top of the viewport. Cancellation is supported via `CancellationToken`.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Call `ScrollToItemAsync` to programmatically scroll to an item after first render. The scroll is instant (no animation). The method returns a `Task` that completes when the target item is aligned to the top of the viewport. Cancellation is supported via `CancellationToken`.
Call `ScrollToItemAsync` to programmatically scroll to an item after the first render. The scroll is instant (no animation). The method returns a <xref:System.Threading.Tasks.Task> that completes when the target item is aligned to the top of the viewport. Cancellation is supported via a <xref:System.Threading.CancellationToken>.


Call `ScrollToItemAsync` to programmatically scroll to an item after first render. The scroll is instant (no animation). The method returns a `Task` that completes when the target item is aligned to the top of the viewport. Cancellation is supported via `CancellationToken`.

If multiple calls occur, the last call wins—earlier calls complete normally but only the final target is honored. If the user scrolls during a programmatic scroll, the user's scroll takes precedence. Calling before first interactive render throws an <xref:System.InvalidOperationException>.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If multiple calls occur, the last call wins—earlier calls complete normally but only the final target is honored. If the user scrolls during a programmatic scroll, the user's scroll takes precedence. Calling before first interactive render throws an <xref:System.InvalidOperationException>.
If multiple calls occur, the last call wins—earlier calls complete normally but only the final target is honored. If the user scrolls during a programmatic scroll, the user's scroll takes precedence. Calling before the first interactive render throws an <xref:System.InvalidOperationException>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants