diff --git a/README.md b/README.md index 1b3f939f57..ce489dfbbe 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,10 @@ - Install with npm: `npm install openlayers` - Clone the repo: `git clone git@github.com:openlayers/ol3.git` +## Supported Browsers + +OpenLayers runs on all modern browsers that support [HTML5](https://html.spec.whatwg.org/multipage/) and [ECMAScript 5](http://www.ecma-international.org/ecma-262/5.1/). This includes Chrome, Firefox, Safari and Edge. For older browsers and platforms like Internet Explorer (down to version 9) and Android 4.x, [polyfills](http://polyfill.io) for `requestAnimationFrame` and `Element.prototype.classList` are required. + ## Documentation Check out the [hosted examples](http://openlayers.org/en/master/examples/), the [workshop](http://openlayers.org/workshop/) or [API docs](http://openlayers.org/en/master/apidoc/). diff --git a/doc/quickstart.hbs b/doc/quickstart.hbs index 03f28e728e..e16490a49f 100644 --- a/doc/quickstart.hbs +++ b/doc/quickstart.hbs @@ -60,6 +60,12 @@ To include a map a web page you will need 3 things: The first part is to include the JavaScript library. For the purpose of this tutorial, here we simply point to the openlayers.org website to get the whole library. In a production environment, we would build a custom version of the library including only the module needed for our application. +**Optional:** If the application is intended to run on old platforms like Internet Explorer or Android 4.x, another script needs to be included before OpenLayers: + +```xml + +``` + ### `
` to contain the map diff --git a/doc/tutorials/introduction.md b/doc/tutorials/introduction.md index 9257e47b46..39ed1f2486 100644 --- a/doc/tutorials/introduction.md +++ b/doc/tutorials/introduction.md @@ -24,7 +24,9 @@ Although Closure library functions are widely used within OL3, none of them are Unlike in, say, Node, where a module's exports are fixed in the source, with Closure Compiler, exports can be defined at compile time. This makes it easy to create builds that are customized to the needs of a particular site or application: a __custom build__ only exports those properties and methods needed by the site or application. As the full build is large, and will probably become larger as new features are added to the API, it's recommended that sites create a custom build for production software. ## Renderers and Browser Support -The library currently includes three renderers: Canvas, DOM, and WebGL. All three support both raster data from tile/image servers, and vector data; WebGL however only supports Point vectors and does not support labels. Clearly only those browsers that [support Canvas](http://caniuse.com/canvas) can use the Canvas renderer. Equally, the WebGL renderer can only be used on those devices and [browsers](http://caniuse.com/webgl) that support WebGL. Internet Explorer versions before 9 are not supported at all. +The library currently includes three renderers: Canvas, DOM, and WebGL. All three support both raster data from tile/image servers, and vector data; WebGL however only supports Point vectors and does not support labels. Clearly only those browsers that [support Canvas](http://caniuse.com/canvas) can use the Canvas renderer. Equally, the WebGL renderer can only be used on those devices and [browsers](http://caniuse.com/webgl) that support WebGL. + +OpenLayers runs on all modern browsers that support [HTML5](https://html.spec.whatwg.org/multipage/) and [ECMAScript 5](http://www.ecma-international.org/ecma-262/5.1/). This includes Chrome, Firefox, Safari and Edge. For older browsers and platforms like Internet Explorer (down to version 9) and Android 4.x, [polyfills](http://polyfill.io) for `requestAnimationFrame` and `Element.prototype.classList` are required. The library is intended for use on both desktop/laptop and mobile devices.