2025-08-28, 09:25:26
Hello Michael,
Thank you for your question.
The property Settings directly exposes the Microsoft CoreWebView2 settings interface - without the wrapper. As such it is probably useless for almost everyone. We should be more clear about that in the help.
A number of the properties in the Settings interface are already available, such as for example the AreBrowserAcceleratorKeysEnabled property is available directly in the AntView interface as BrowserAcceleratorKeysEnabled property.
Adding an extra "Settings" interface for these, although very descriptive, didn't make a lot of sense to us as each interface means needing more scaffolding code in the target development environment.
We'll look into the HiddenPdfToolbarItems property and will contact you by email when we have something that works.
--
Wil
Thank you for your question.
The property Settings directly exposes the Microsoft CoreWebView2 settings interface - without the wrapper. As such it is probably useless for almost everyone. We should be more clear about that in the help.
A number of the properties in the Settings interface are already available, such as for example the AreBrowserAcceleratorKeysEnabled property is available directly in the AntView interface as BrowserAcceleratorKeysEnabled property.
Adding an extra "Settings" interface for these, although very descriptive, didn't make a lot of sense to us as each interface means needing more scaffolding code in the target development environment.
We'll look into the HiddenPdfToolbarItems property and will contact you by email when we have something that works.
--
Wil