You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest that the feature of Always On Top enhance the stroke to be round-cornered in order to fit the UI Design of Windows 11.
Scenario when this would be used?
See, if I enable the stroke option, the rectangle lines would look strange and sharp and hard while the outlines of the current window are round-cornered.
It would look much better and unified when changed into a round-cornered style.
Of course, there are still many Power Users running Windows 10, but would you please take your time to improve the experience of the growing number of Windows 11 users?
Supporting information
No response
The text was updated successfully, but these errors were encountered:
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
ghost
added
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
and removed
Needs-Triage
For issues raised to be triaged and prioritized by internal Microsoft teams
labels
Apr 23, 2022
Description of the new feature / enhancement
I suggest that the feature of Always On Top enhance the stroke to be round-cornered in order to fit the UI Design of Windows 11.
Scenario when this would be used?
See, if I enable the stroke option, the rectangle lines would look strange and sharp and hard while the outlines of the current window are round-cornered.
It would look much better and unified when changed into a round-cornered style.
Of course, there are still many Power Users running Windows 10, but would you please take your time to improve the experience of the growing number of Windows 11 users?
Supporting information
No response
The text was updated successfully, but these errors were encountered: