MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Page Setup reinstates missing properties and detect if print window is open

Open
#2,134 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Page Setup reinstates all the missing configuration properties for header / footer that were in ChtmlView.

If I have the print preview open I can still close my main application - can't we detect the print preview window is visible to prevent this?

All of those things to my knowledge can't be done yet with WebView2 and would cripple my application behaviour. It seems that the developers are thinking it just the terms of a browser and thus you will probably have it maximised anyway. But it is also being used as a control - so not always full screen. And this forcing the print preview to the confines of the browser makes it not useable.

I have raised all of these things before and to my knowledge there have been no fixes for any of them???

Originally posted by @ajtruckle in https://github.com/MicrosoftEdge/WebView2Feedback/issues/871#issuecomment-1029406850

AB#38054655

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the WebView2 Page Setup and print preview capabilities, including the limitations described in the linked prior discussion. Done would require restoring the missing header/footer configuration properties and providing a way to detect a visible print preview window so the main application cannot close unexpectedly.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.