#DYMO LABEL WEB SERVICE FULL#
However, I think the important one is "unaware" because when I run full screen I expect the window size in javascript to be reported near 3840x2160, but it reports as around 2500x1440. The one that starts "-type=renderer" is "Unaware" Specifically, the one that starts "-embedded-browser-webview=1" is Per-Monitor (v2)
My exe name shows for "-webview-exe-name" on some that are Per-Monitor and some that are "Unaware" 4 of them report "Per-Monitor (v2)" and 2 "Unaware". When my app launches, there are 6 processes listed for msedgewebview2.exe. You can see which process corresponds to your app by checking the command line for -webview-exe-name=. Task Manager > Details tab > Command Line column > DPI Awareness column You can try looking at the msedgewebview2.exe process for your app in Task Manager and see if they are running as DPI aware. Issue persists when there is only one monitor and it is scaled.ĭPI scaling should work if gdiScaling is false. It doesn't matter which monitor is primary/secondary or even IF there is a secondary monitor. Note that I can repro the images below by simply dragging the form from one window to the other.
#DYMO LABEL WEB SERVICE WINDOWS#
What do I need to do to make this display properly on a scaled monitor?Ĭreate a windows form.
I tested the size of the webview control and even though it's taking up 25% of the form, the actual pixel size is the same as the form. If I move the form to my non-scaled monitor, it displays properly. (Monitor scaled at 200%.) So when I open the form on my high DPI monitor, the webview control takes up about 25 of the total form, even though it's docked to take up the entire form. Here's the problem: My webview2 control is NOT scaling. My entire app is scaling properly (on high DPI monitors) using these settings in the app.manifest: Support is going away, so I am upgrading to the new webview2 control. I have a form on which I was using the old webbrowser control. I just didn't see any documentation pointing to this issue and want to save other users the headaches this has caused us and our customers. merchantAuthenticationType myMAT = new merchantAuthenticationType ItemElementName = ansactionKey,Īnd that the overload constructor for each request (ie: createTransactionRequest) allows to pass the MerchantAuthentication object in real-time, and fix this issue. I opened this issue - so that the documentation can be updated to notate, this is NOT THREAD SAFE, ApiOperationBase.MerchantAuthentication = new merchantAuthenticationType() I see there is an overload method for each request object which allows us to push the MerchantAuthentication object in. But we have 100's of customers each with their own Transaction ID and Key, processing hundreds of transactions. I suspect the abstract class with static method approach works for 98% of the public because they are always accessing the same gateway account (Transaction ID and Key). This has lead to huge consequences and reliability, where we are seeing payments being processed into the wrong merchant account (because the Transaction ID and Key) are being overwritten when multiple threads are accessing this static method at the same time. The MerchantAuthentication approach provided in the documentation is not thread safe and leads to concurrency issues.
Or, perhaps there is a way to get the file open dialog into the host UI thread. Running Edge as elevated works as expected. The DevTools call DOM.setFileInputFiles is not functional so not a viable workaround at this time. Navigate to page with a file input (for example,, click image icon and then Upload Images tag)Įxpectation: we need a mechanism to call back into our elevated app to present the File UI, and return/send back the selected files. Launch WinForms sample app as administrator Running the renderer as elevated would create other issues, such as not being able to drag/drop onto the view.Ĭonsidering some apps require elevation for a variety of purposes, this limits the usefulness of webview2. This is presumably because the renderer process is not elevated and so cannot display a window in an elevated process. When running application "as administrator" (elevated), the File Open dialog will not appear from a file input element.