fix(Command): prevent scroll blocking when groups are not used

[DAHNEEV]

When using Command.Item exclusively (without grouping, etc.), the view fails to scroll to the first element even though the focus successfully shifts to it.

<Command.List>
  <Command.Viewport>
    <Command.Item></Command.Item>
    <Command.Item></Command.Item>
    ...
  </Command.Viewport>
</Command.List>

123.mov

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8f0f35e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
bits-ui	✅ Ready (View Log)	Visit Preview	8f0f35e

[sami-suleiman]

Hi, we hit this bug too: in a scrollable Command list with a heading-less group, navigating to the first item (e.g. Home) selects it but doesn't scroll it into view, because scrollSelectedIntoView returns early even when there is no heading to scroll.

I tested this PR's change against our repro on 2.18.1: without it the first item is never scrolled, with it it is. So it fixes the root cause for us, and we could drop our local workaround.

What's the current status? If anything is missing (tests, changeset, rebase), I can help.