DPI change is not fully handled in the cascading window on Windows

Description

Spun off from #1604.

This is something I overlooked in my #1481 for #1459.

mozc::renderer::win32::WindowManager::UpdateLayout forgot to call cascading_window_->UpdateDpi(target_dpi).

mozc/src/renderer/win32/window_manager.cc

Lines 235 to 244 in e5f1494

    
           // Sync both windows to the DPI of the monitor where the candidate window 
        
           // is about to be placed. This makes their first-frame layout correct when 
        
           // the target app is on a different-DPI monitor than where the windows were 
        
           // last shown — WM_DPICHANGED would otherwise fire only during the 
        
           // subsequent SetWindowPos, after the size has already been computed at 
        
           // the stale DPI. 
        
           const uint32_t target_dpi = GetDpiForPoint(target_point.x, target_point.y); 
        
           main_window_->UpdateDpi(target_dpi); 
        
           infolist_window_->UpdateDpi(target_dpi);

As a result, the cascading window remains to be the initial DPI even when it should use a newer value.

Steps to reproduce

Install Mozc for Windows
Open Notepad then enable Mozc.
Type something then hit the space key multiple times to show the cascading window.
Change the display DPI in the system settings.

Expected behavior

The cascading window is scaled up/down accordingly.

Actual behavior

The cascading window remains to use the initial DPI.

Screenshots

DPI 200% -> 100%

DPI 200% -> 200%

DPI 200% -> 300%

Version or commit-id

e5f1494

Environment

OS: Windows 11 26H2

Fix stale DPI in the cascading window on Windows (google#1610)

Navigation Menu

Repository navigation

DPI change is not fully handled in the cascading window on Windows #1609

Description

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

DPI 200% -> 100%

DPI 200% -> 200%

DPI 200% -> 300%

Version or commit-id

Environment

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	// Sync both windows to the DPI of the monitor where the candidate window
	// is about to be placed. This makes their first-frame layout correct when
	// the target app is on a different-DPI monitor than where the windows were
	// last shown — WM_DPICHANGED would otherwise fire only during the
	// subsequent SetWindowPos, after the size has already been computed at
	// the stale DPI.
	const uint32_t target_dpi = GetDpiForPoint(target_point.x, target_point.y);
	main_window_->UpdateDpi(target_dpi);
	infolist_window_->UpdateDpi(target_dpi);

DPI change is not fully handled in the cascading window on Windows #1609

Description

Description

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

DPI 200% -> 100%

DPI 200% -> 200%

DPI 200% -> 300%

Version or commit-id

Environment

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions