Modern WebKit Engine and Invalid Certificates
Since Version 2.2 of the WebKit plugin we support both, the modern and legacy WebKit engines.
While the modern engine has several advantages (see below) it also has some shortcomings in its current iteration. One of those is the inability to handle invalid (self-signed) certificates on macOS 10.10 Yosemite. Apple already fixed this in macOS 10.11 El Capitan but there's a workaround available for Yosemite too:
- Open the site with the invalid certificate in Safari
- Wait for the certificate prompt to appear
- Click "Show Certificate"
- Click "Always trust..." to store the trust in the Keychain
- Click "Continue"
Like mentioned above, this workaround is only required on Yosemite. The WebKit engine shipped with El Capitan properly supports certificate validation so this workaround is not required.
WebKit and flipped Web Plugins after switching tabs
There's unfortunately a bug in Apple’s WebKit framework when using web plugins in 64 bit applications that causes web plugins embedded in a page to flip once the underlying window or view becomes invisible. Since Royal TSX uses tabs to separate connection sessions from each other, it is affected by this bug.
WebKit Plugin and Java
Update: A new beta version of the WebKit plugin is now available that offers the choice of using the legacy or modern WebKit engine. Among other improvements, the modern engine has the advantage of properly supporting Java.
Blocked Plug-in with WebKit
Tags: Web HTTP HTTPS WebKit HTML Java Flash Plugin Plugins