{Freeway-Bug; Linked:Bug1641193; LinkedBug}[FancyZones Editor]: FancyZones editor window does not adapt 225% resize mode setting.

[Priyanka-Chauhan123]

Microsoft PowerToys version

"0.35.0"

Running as admin

• Yes

Area(s) with issue?

FancyZones Editor

Steps to reproduce

Test Environment:
OS: Windows 10 Build 21354.1
App version: 0.35.0
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

Pre-Requisite:

1. Go to settings > Display settings > Set the resolution to 1280*768.
2. Set the slider value to maximum i.e. 225% (Settings -> Ease of access -> text scaling) and Apply.

Repro Steps

1. Launch 'PowerToys' application.
2. Application will get open with default list item 'General' selected.
3. Navigate to 'FancyZones' at the left side of the pane and activate it.
4. Now navigate to 'Launch layout editor' button and activate it.
5. FancyZones editor window will get open.
6. Observe the issue.

User Impact: Priority-1
If any application does not support resizing of text without loss of content or functionality, the users with mild visual disabilities who scales the text instead of using the assistive technology would be impacted as zooming will not work as desired.

MAS Reference:
https://microsoft.sharepoint.com/:w:/r/sites/accessibility/_layouts/15/Doc.aspx?sourcedoc=%7B5BE8E205-7508-414C-A273-657770321DA0%7D&file=MAS%201.4.4%20%E2%80%93%20Resize%20Text.docx&wdLOR=cD434D0F2-F515-4FD8-B4DA-BA99282968ED&action=default&mobileredirect=true&cid=e8a7e0cb-a049-4c6a-b020-862f20088e4c

MAS1.4.4_Edit zone editor window not adapting resize setting.zip

✔️ Expected Behavior

FancyZones editor window should adapt 225% resize mode setting.

❌ Actual Behavior

FancyZones editor window does not adapt 225% resize mode setting.

Other Software

No response

[yuyoyuppe]

I believe this is blocked until we port FZE to UWP.

Ability to scale text for accessibility was initially added to UWP, but then was implemented in WPF as a patch (?).

The crucial difference between the implementations is that the text elements with FontSize property are not affected by system font scaling setting value in WPF apps, while they are affected in UWP apps. That could be tested easily by creating blank UWP/WPF apps with a following element:

<TextBlock Text="THE TEXT" FontSize="24"/>

and then changing the system-wide font scaling and observing the (lack of) changes.

In FZE we also use ui:WindowHelper.UseModernWindowStyle="True", which, among other things, sets default sizes for all TextBlock elements.

Even if we don't rely on ModernWPF default styles and reinvent them ourselves, we'll need to have a way to subscribe to font scale change events. It's easy in UWP, since it has UISettings.TextScaleFactorChanged event, but we'll have to rely on, as far as I understand, an undocumented registry value for that in WPF. Then we could use VisualTreeHelper to traverse the whole app's tree to set new FontSizes manually for all required elements. The other alternative is to inherit from TextBlock,Label... etc. standard control classes and create an event channel which would be raise events triggered by registry value changes.

I don't think any of the options described above are worth it, though I'm not a WPF expert, so I might be missing something here.

cc: @crutkas @niels9001

[niels9001]

Yeah, I've always struggled with scaling and WPF. A lot of that solves itself by moving to WinUI / XAML Islands.

[batzen]

I guess it's because the editor is missing an app.manifest file where dpi awareness has to be declared.
Example https://github.com/fluentribbon/Fluent.Ribbon/blob/develop/Fluent.Ribbon.Showcase/app.manifest
You should be able to just copy that file and replace Fluent.Ribbon with something else.

[yuyoyuppe]

Thanks for the suggestion! I've tried coping <application xmlns="urn:schemas-microsoft-com:asm.v3"> to our app.manifest but it didn't have any effect. I guess that's because the system option is not directly related to dpi, but to accessibility?

[batzen]

Ah, my fault. I thought DPI = scale. Never used the slider for text and even forgot that it exists.

[crutkas]

Marking blocked as of now, dotnet/wpf#5405 lacks enough info for us to move forward as we don't have a way to get current scale.

[crutkas]

revisit in 53 to see if there is a fix

[Priyanshu073]

Hello @crutkas

Kindly provide component's URL or code pen or any other details from where the UI and other components were picked such that, such that partner team can identify the component.

[crutkas]

see #10766 (comment)

dotnet/wpf#5405

[Priyanshu073]

This issue is not reproducible after changing the DPI method setting(custom scaling to 200%). Hence closing this bug.