[RangeSelector] on WASM draws squares around track controls

[xperiandri]

Describe the bug

Steps to reproduce

Create a blank Uno app
Add a `RangeSelector` to the main page
Launch WASM head

Expected behavior

No square borders around track controls

Screenshots

No response

Code Platform

• UWP
• WinAppSDK / WinUI 3
• Web Assembly (WASM)
• Android
• iOS
• MacOS
• Linux / GTK

Windows Build Number

• Windows 10 1809 (Build 17763)
• Windows 10 1903 (Build 18362)
• Windows 10 1909 (Build 18363)
• Windows 10 2004 (Build 19041)
• Windows 10 20H2 (Build 19042)
• Windows 10 21H1 (Build 19043)
• Windows 10 21H2 (Build 19044)
• Windows 10 22H2 (Build 19045)
• Windows 11 21H2 (Build 22000)
• Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

• Windows 10, version 1809 (Build 17763)
• Windows 10, version 1903 (Build 18362)
• Windows 10, version 1909 (Build 18363)
• Windows 10, version 2004 (Build 19041)
• Windows 10, version 2104 (Build 20348)
• Windows 11, version 22H2 (Build 22000)
• Other (specify)

Other SDK version

No response

Visual Studio Version

2022

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

Yes, but only if others can assist.

[Arlodotexe]

Looks like Uno had fixed this in this PR. This can be reproduced over in https://toolkitlabs.dev, which is using the latest version of Uno from our main branch. This appears to be a regression in Uno.

[michael-hawker]

This is an Uno issue, their bug is here: unoplatform/uno#10263, it was supposed to have been fixed, hmm.

[xperiandri]

So why do they appear if it is fixed?
Or is not it fixed?

[michael-hawker]

So why do they appear if it is fixed? Or is not it fixed?

It was supposedly fixed, but that appears to not be the case. I thought I had seen this work in the interim at one point, so maybe it regressed again. I poked the Uno issue, so that's going to be the best place to follow-up.

[xperiandri]

Thanks

[MartinZikmund]

The linked issue is not related, we are tracking this in unoplatform/uno#15448, will prioritize it to get the fix out asap