<ahref="#Current_state_of_the_SWT_HTML_Browser_by_operating_systems"><spanclass="tocnumber">5</span><spanclass="toctext">Current state of the SWT HTML Browser by operating systems</span></a>
SWT provides 3 different modes for its Web Browser: mozilla, webkit and none. These can be configured through /xowa/user/anonymous/app/os_name.gfs with the following snippet:
<ahref="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/XULRunner"rel="nofollow"class="external text">XULRunner</a> is a runtime package provided by Mozilla that can be used to build Firefox-like applications. It can be deployed in a standalone package that does not interfere with any installed versions of Firefox.
</p>
<p>
The download location for xulrunner is <ahref="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/"rel="nofollow"class="external free">http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/</a>
</p>
<p>
XOWA includes xulrunner at /xowa/operating_system_name/xulrunner . For example, on Linux 64-bit, this folder is at /xowa/linux_64/xulrunner/
</p>
<p>
XOWA can use different versions of xulrunner with something like the following snippet:
Mozilla Firefox has Extended Support Releases (ESRs). These start at version 10 and occur at 7-step intervals: 10, 17, 24, 31, 38.
</p>
<p>
Each version of SWT limits compatibility to a specific XULRunner ESR. For SWT version 4.5, the highest XULRunner is 31. Also, non-ESR versions are not allowed. For example, SWT will fail if using XULRunner v30.
SWT can also be configured to use the system's default WebKit browser. In most cases, this relates directly to Safari and is easiest done on a Mac OS X system. It can be done for Linux / Windows, but further steps need to be taken. See <ahref="https://www.eclipse.org/swt/faq.php#howusewebkit"rel="nofollow"class="external free">https://www.eclipse.org/swt/faq.php#howusewebkit</a>
</p>
<p>
XOWA may support WebKit on Linux / Windows at a future date, but for now, it is not a backlog item. If you are interested, please contact me and I will reevaluate.
SWT can also be configured to use the system's browser through the keyword "none". For all intents and purposes, this basically applies to using Internet Explorer on Windows machines.
</p>
<p>
XOWA does not support Internet Explorer. It may do so in the future, but it would be dependent on the ease of the Javascript / CSS integration.
<spanclass="mw-headline"id="Current_state_of_the_SWT_HTML_Browser_by_operating_systems">Current state of the SWT HTML Browser by operating systems</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/wiki/App/UI/HTML_Browser?action=edit&section_key=Current_state_of_the_SWT_HTML_Browser_by_operating_systems"title="Edit section: Current_state_of_the_SWT_HTML_Browser_by_operating_systems"class="xowa-hover-off">edit</a><spanclass="mw-editsection-bracket">]</span></span>
As of v2.6.5, XOWA uses XUL Runner 24 for both Windows 32 bit and Windows 64.
</p>
<p>
XULRunner 31 does work with Windows XP and Windows 7, but there have been reports of failure on Windows 8. As a result, 24 is the official package.
</p>
<p>
There is one known issue wherein an error message appears in the console: <code>1435372844657 addons.manager ERROR startup failed: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIPrefBranch.setCharPref]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: resource://gre/modules/AddonManager.jsm :: AMI_startup :: line 645" data: no] Stack trace: AMI_startup()@resource://gre/modules/AddonManager.jsm:645 < AMP_startup()@resource://gre/modules/AddonManager.jsm:2318 < AMC_observe()@resource://gre/components/addonManager.js:55 <<file:unknown></code>
</p>
<p>
However this appears to be benign. There is also currently an open bug on it. <ahref="https://bugs.eclipse.org/bugs/show_bug.cgi?id=466391"rel="nofollow"class="external free">https://bugs.eclipse.org/bugs/show_bug.cgi?id=466391</a>
<spanclass="mw-headline"id="Mac_OS_X">Mac OS X</span><spanclass="mw-editsection"><spanclass="mw-editsection-bracket">[</span><ahref="/wiki/App/UI/HTML_Browser?action=edit&section_key=Mac_OS_X"title="Edit section: Mac_OS_X"class="xowa-hover-off">edit</a><spanclass="mw-editsection-bracket">]</span></span>
The app package also includes XULRunner 31, but this is not enabled by default. The main issue is that mouse events are not relayed from XULrunner to SWT: <ahref="https://bugs.eclipse.org/bugs/show_bug.cgi?id=246830"rel="nofollow"class="external free">https://bugs.eclipse.org/bugs/show_bug.cgi?id=246830</a> . As a result, mouse hover does not work, and XOWA popups will not show.
</p>
<p>
WebKit appears to be mostly functional, but it doesn't handle cursor changes. Hovering over a link won't change the cursor to a hand cursor. This appears to be an SWT issue, though the only known ticket is closed: <ahref="https://bugs.eclipse.org/bugs/show_bug.cgi?id=237562"rel="nofollow"class="external free">https://bugs.eclipse.org/bugs/show_bug.cgi?id=237562</a>
Unfortunately, XULRunner 31 is not yet implemented by SWT. See: <ahref="https://bugs.eclipse.org/bugs/show_bug.cgi?id=437700"rel="nofollow"class="external free">https://bugs.eclipse.org/bugs/show_bug.cgi?id=437700</a>
</p>
<p>
Furthermore, XULRunner 24 requires GTK3 to be disabled since XULRunner is not yet ported to GTK3. See: <ahref="https://bugs.eclipse.org/bugs/show_bug.cgi?id=423870"rel="nofollow"class="external free">https://bugs.eclipse.org/bugs/show_bug.cgi?id=423870</a>
</p>
<p>
XOWA accomplishes this by running the following in the xowa_linux_64.sh file "export SWT_GTK3=0 && java -jar xowa_linux_64.jar"
<li><ahref="http://dumps.wikimedia.org/backup-index.html"title="Get wiki datababase dumps directly from Wikimedia">Wikimedia dumps</a></li>
<li><ahref="https://archive.org/search.php?query=xowa"title="Search archive.org for XOWA files">XOWA @ archive.org</a></li>
<li><ahref="http://en.wikipedia.org"title="Visit Wikipedia (and compare to XOWA!)">English Wikipedia</a></li>
</ul>
</div>
</div>
<divclass="portal"id='xowa-portal-donate'>
<h3>Donate</h3>
<divclass="body">
<ul>
<li><ahref="https://archive.org/donate/index.php"title="Support archive.org!">archive.org</a></li><!-- listed first due to recent fire damages: http://blog.archive.org/2013/11/06/scanning-center-fire-please-help-rebuild/ -->