The website I'd like to use in Royal TSX doesn't work with Safari/WebKit

Most website today work properly with WebKit. If you still encounter a page that doesn't seem to behave properly, there's one trick that might help: Fake the "User Agent String".
The user agent string is used by some website to identify the browser that you're using. Since Royal TSX is not Safari, we don't pretend to be Safari and our user agent string differs from that of Safari. You can however overwrite the user agent string in the "Advanced" section of your web page's properties. Enable "Use Custom User Agent String" and specify the string to use in the textbox below. If, for instance, you want to use the same user agent string as Safari, open a new Safari window and navigate to whatsmyuseragent.org, then copy the string it outputs and paste it in Royal TSX. Of course, the same procedure can be used to fake Chrome's user agent string.


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"
As soon as the trust is stored in the Keychain you should be able to connect with Royal TSX too.
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

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 web plugins.

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. 

Since Royal TSX V1 was a 32 bit application it wasn’t affected by the bug.

We have an open ticket with Apple about this. They acknowledged it’s a bug but haven’t provided a workaround nor a time frame for a fix.

Here are some references about the issue:

http://openradar.appspot.com/19701304

http://stackoverflow.com/questions/28305904/webview-in-nstabview-and-sethostwindowyes-causing-flipped-plugins

https://devforums.apple.com/message/1098924#1098924

We'll update this article when new information becomes available.

WebKit Plugin and Java

This section applies to Royal TSX 2.X:

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.

Unfortunately, the current state of support for Java in Apple's WebKit Framework is unknown. In Yosemite, it doesn't appear to work even using the most basic setup.

We have an  open ticket  with Apple about this and will update this article once new information becomes available.

This section applies to Royal TSX 1.X:

Like Google Chrome, Royal TSX is a 32 bit application and requires the 32 bit version of Java which is only available until version 6.

So if you already have Java 7 installed you have to downgrade to version 6.

To downgrade to Java 6, you can follow this guide:  http://support.apple.com/kb/HT5559



Blocked Plug-in with WebKit

Apple introduced a  new feature  in Safari for macOS 10.9 Mavericks that by default blocks plugins to save energy.

Because Royal TSX' WebKit plugin is based on Safari it inherits Safari's settings to a certain degree, including the power saver whitelist.

So if you stumble upon a website that greets you with a "Blocked Plug-in" message, make sure that website is on the whitelist for websites that may start plug-ins automatically.

For more info on the subject and steps to resolve the issue please head over to  this TekRevue post .