Browser Compatibility¶
Supported Browsers¶
MOTECH project uses new technologies (HTML 5, CSS3) and new frameworks like AngularJS, Bootstrap which means that the compatibility of the browsers depends on the extent to which these frameworks support old browsers.
Specifically, we support the latest versions of the following browsers and platforms.
Platform | IE 10+ | Chrome | Firefox | Safari | Opera |
---|---|---|---|---|---|
Windows | Supported | Supported | Supported | Not Supported | Supported |
Mac OS X | Not Supported | Supported | Supported | Supported | Supported |
Linux | Not Supported | Supported | Supported | Not Supported | Supported |
Unofficially, MOTECH should look and behave well enough in Chromium for Linux, though it is not officially supported.
Internet Explorer Compatibility¶
Bootstrap is built to work best in the latest desktop browsers, meaning older browsers might display differently styled, though fully functional, renderings of certain components.
AngularJS 1.3 has dropped support for IE8. Read more about it on this blog.
The AngularJS project currently supports and will attempt to fix bugs for IE9 and above. Their continuous integration server runs all the tests against IE9, IE10, and IE11. See Travis CI and ci.angularjs.org.
Screen Resolution¶
Currently we tested MOTECH on screen resolution 1024 x 768 px and higher, but the best results will be achieved using resolution 1680 x 1050 px or higher, especially for wide tables. That means we do not support mobile and tablet devices.
Browser Settings¶
All browsers must have cookies and JavaScript enabled to use MOTECH.
Our approach to maintain compatibility with browsers¶
- Even if we declare the latest HTML 5 in MOTECH, we try not to use the latest tags, if possible.
- Newer versions of browsers provide debugging tools directly or as a plugin. These developer tools also allow you to inspect specific HTML and alter CSS styles.
- We do not use inline JavaScript events inside HTML markup. An example would be <button onclick=”validate()”>Validate</button>. This practice breaks the clean separation that should exist between markup, presentation, and behavior.