NuGet / Home

Repo for NuGet Client issues
Other
1.5k stars 252 forks source link

[Bug Bash][ARM64] The left border of the searched result list doesn’t left-align with the left border of the search box on VS ARM64 #12490

Closed v-longmin closed 7 months ago

v-longmin commented 1 year ago

NuGet Product Used

Visual Studio Package Management UI

Product Version

Dev\6.6.0.52

Worked before?

No response

Impact

It bothers me. A fix would be nice

Repro Steps & Context

Repro Steps: 

  1. Create a new C# console App (.NET Core) project on VS ARM 64.
  2. Open the PM UI of the project and go to the “Browse” tab.
  3. Search “AutoMapper” package in Browse tab. (The string has been searched before.)
  4. Click drop-down and observe the position of the left border of the searched result list.

    Expected: 

    The left border of the searched result list should be left-align with the left border of the search box. 

    Actual: 

    The left border of the searched result list doesn’t left-align with the left border of the search box as below screenshot. image

    Note:

    1.The issue doesn’t repro on VS x64. 2.It’s not a regression since it reproduced on D17.3\32611.02.

Verbose Logs

No response

nkolev92 commented 1 year ago

Team Triage: @martinrrm can you please take a look to see whether we use a VS or WPF built in control? It's our problem only if we're writing our own control.

nkolev92 commented 1 year ago

Assigning to hotseat to confirm whether the problem is on our end or with any of the common controls.

martinrrm commented 1 year ago

I have tested in two ARM64 machines and could't reproduce this in VS Internal.

image image

jeffkl commented 1 year ago

Team Triage: @v-longmin Martin was unable to repro this, see https://github.com/NuGet/Home/issues/12490#issuecomment-1499415958. Does it still repro for you, can you maybe provide is access to a VM where its happening?

donnie-msft commented 1 year ago

Team Triage: @martinrrm can you please take a look to see whether we use a VS or WPF built in control? It's our problem only if we're writing our own control.

We do not own the control, it's a VS Search box control. That doesn't mean some layout or styling of ours can't affect it.

ghost commented 1 year ago

This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment.

v-luzh commented 1 year ago

Hi @martinrrm, it still reproes on D17.6\33712.159. We will reopen it. Please help to have a look, thanks.

jebriede commented 1 year ago

Team Triage: @v-luzh can you please provide us access to a VM offline so we can see the repro? Thanks!

v-luzh commented 1 year ago

Hi @jebriede, we didn't do the testing on ARM64 VM. We met the bug on ARM64 phisical machine Surface Pro X.

donnie-msft commented 1 year ago

@v-luzh is this Win11? Could you post the Windows installation version found by running winver from a command prompt?

Also, what are the properties of your Display found under: Start -> "make everything bigger" -> scaling %? Start -> "resolution" -> "Scale and layout" -> scaling %? Start -> "resolution" -> "Scale and layout" -> screen resolution?

v-luzh commented 1 year ago

Hi @donnie-msft, yes it's Windows 11 Pro 22H2 (OS build 22621.1702). The info of Display is as below. image

martinrrm commented 1 year ago

I'll try again and see if changing scale/resolution is the problem.

ghost commented 1 year ago

This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment.

SueSu01 commented 7 months ago

Verified this issue on VS D17.10\34804.81 + NuGet Client Dev\6.10.0.97, it's fixed, so closed it, thanks! image