Anyone else seeing previously stable desktop code using HTMLViewer control failing in 2020 R1?

Thanks for the lead. Point is, my prior version worked fine in 2019R3.x, and failed under 2020R1, so something changed in how the HTMLViewer operates, and that appears as I wrote above. I’ll think about your idea Rick, and am loath to yet again tear apart good working code in the name of progress.

[image] Rick_Araujo: LoadPage(HTMLstring, folderItemAnyFileBase) Here’s another one … HTMLViewer 2019RX would open a file without a file extension, for example a temp file. R20 won’t, so more code changes.

The Release Notes for 2020r1 says: Updated HTMLViewer on macOS to use WKWebView.

Yup. Yet it does not say what, exactly, that changed. For those using HTML quite a bit for desktop apps, we get to find out by the hard way.

WKWebView is the new Apple class and you’d almost have to read the description on Apples site as to what it changes from the old underlying class (WebView I believe)

sadly, 2020R1 isn’t ready for prime time IMHO. Here’s another one: simple new desktop app. Add an HTMLViewer and a canvas. Set a backdrop and make the canvas visible. In R19, the zorder set by IDE is honored … set canvas to topmost and it obscures the HTMLviewer. In R20 zorder is ignored and the H…

[image] Hank_Marquis: Add an HTMLViewer and a canvas. Set a backdrop and make the canvas visible. I get this with Xojo2020r1: [canvas]

I get this with Xojo2020r1: [Screen Shot 2020-09-02 at 5.34.39 PM] Doesn’t matter which I choose to be at the top of the z-order… I get this with Xojo2019r3: [Screen Shot 2020-09-02 at 5.41.26 PM]

you could fade any website using javascript: For example after document complete event: HTMLViewer.ExecuteJavascript "document.body.style.opacity = 0.5;" 0.0 = invisible page 1.0 = completely visible page. This works better than having a canvas over it, much less cpu, mem and less work…

Xojo Programming Forum

Desktop HTML viewer fail with 2020 R1

Targets macOS