Incompatibilities between Eclipse 4.7 and 4.8

Eclipse changed in incompatible ways between 4.7 and 4.8 in ways that affect plug-ins. The following entries describe the areas that changed and provide instructions for migrating 4.7 plug-ins to 4.8. Note that you only need to look here if you are experiencing problems running your 4.7 plug-in on 4.8.

See also the list of deprecated API removals for this release.

  1. Support for XULRunner dropped

1. Support for XULRunner dropped

What is affected: Clients that use SWT.MOZILLA style in org.eclipse.swt.browser.Browser#Browser(Composite parent, int style) constructor.


Eclipse/SWT has dropped support for XULRunner as a browser rendering engine on all platforms.

SWT.MOZILLA style is deprecated. When it is used in the SWT Browser constructor org.eclipse.swt.browser.Browser.Browser(Composite, int), it'll be ignored and the browser will be created with SWT.NONE style, if no other style is specified.

Action required: Clients should replace occurrences of SWT.MOZILLA in the code with SWT.NONE or SWT.WEBKIT.