Hi All - just checking whether anyone else is getting this before I report a bug.
We are in the process of releasing a sizeable system at present with about a dozen copies going out to beta testers. With 2017.1 just popping up, it was obvious to recompile and ship out the latest release so that we don’t have to go through the same rigmarole all over again. Then we hit a show stopper.
While managerial access to the application displays pretty conventional dialogs, the front-end is HTML based using the HTMLViewer, themes stored on disk, dynamically generated content and the use of CancelLoad etc. to both load new pages, dynamically modify existing displays and so on.
Everything works fine in Mac 2016.4.1 and 2017.1 and Win 2016.4.1, in Native and WebKit, as well as being fine Native in Win 2017.1 - so we know that it is not errors in the existing code. We can’t use native as there are features / opportunities that we want from Webkit, as well as making sure that we have a standard roll-out to all the clients. The problems described below are on a pretty new Win10 machine, fully updated to latest OS release.
Bug 1: Web pages are unable to find background images. Standard CSS code indicating a background image. Works find in all other environments, but in Win 2017.1 WebKit, remains white screen. Same with background images of pseudo buttons etc.
Bug 2: Cursor changes to a hyperlink finger on mouseover of links, but the link doesn’t fire when clicked. Placed a breakpoint on the first line of code in CancelLoad - nothing - CancelLoad is not being fired. Again, works fine in all other environments described above.
Bug 3: As there are differences in what Win browsers produce as a URL in CancelLoad (i.e. a prefix with ‘file:///’ in some situations) we guessed this and modified the links to be standard ‘http://’ prefixes as a test. Again, works fine in all other environments describe above, but then fires three times in Win 2017.1 on a single click.
Anyone else seeing this? Last thing I want to do is switch to 2017.1 only to find half of the methods that we are relying on in 2016.4.1 no longer work because of WebKit on Windows, rather than being a straight-up fixable bug in Xojo.