OL 6.9.0 does not work in IE11
See original GitHub issueI downloaded the latest release of OL 6.9.0
Created a simple website:
<!DOCTYPE html>
<html>
<head>
<title>Base map</title>
<meta charset="utf-8">
<script src="ol.js"></script>
<link rel="stylesheet" href="ol.css">
<style>
html, body, .map {
font-family: sans-serif;
width: 100%;
height: 100%;
margin: 0;
padding: 0;
}
</style>
</head>
<body>
<div id="map" class="map"></div>
<script>
var map = new ol.Map({
target: 'map',
view: new ol.View({
center: [ 4083008.076023652,6555612.176249601 ],
zoom : 14
}),
layers: [
new ol.layer.Tile({
baselayer: true,
zIndex : 0,
visible: true,
source : new ol.source.OSM()
}),
]
});
</script>
</body>
</html>
In Chrome, FF, EDGE, Opera, Vivaldi I see a map
But in IE11 I see a blank page and get an error: “Symbol” is undefined ol.js (2,11750)
I tried to configure “webpack-config-legacy-build.js” adding the option “ie 11” or “ie10” and even “ie9” there (and: npm run build-legacy) - the assembly does not change…
export default {
entry: ['regenerator-runtime/runtime', './build/index.js'],
devtool: 'source-map',
mode: 'production',
target: ['web', 'es5'],
module: {
rules: [
{
test: /\.m?js$/,
use: {
loader: 'babel-loader',
options: {
presets: [
[
'@babel/preset-env',
{
targets: 'ie 11, last 2 versions, not dead',
},
],
],
},
},
},
],
},
//...
How do I build for older browsers?
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
OpenLayers: Does not work in internet explorer - Stack Overflow
new OpenLayers.Layer.OSM(). does't work for me on IE11 as well. I tried with https scheme since there was changes with redirecting from http ......
Read more >OpenLayers v7.2.2 API - Class: Map
The map is the core component of OpenLayers. For a map to render, a view, one or more layers, and a target container...
Read more >Browser Mode for MS Edge not working on Blue Prism 6.9
Hi, I'm trying to spy elements on a webpage on Microsoft Edge with Blue Prism 6.9, but it looks like the browser spy...
Read more >Release 6.x - Adaptavist Documentation
Check out what's new for ScriptRunner for Bitbucket Server. 6.29.0. This version is not compatible with IE11. Do not update to this version...
Read more >Release Notes - Profields Server and Data Center - Confluence
NEW FEATURE View Issues: This functionality will allow every user to search ... box is not shown anymore; FIXED BUG Users with Internet...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
#12891 should fix this. The examples need GeoTIFF dependencies to be transpiled to ES5 syntax. The legacy build needs either a polyfill or mock definition for Reflect. The polyfil.io Reflect definition does not support typed arrays and throws an error. Either use a better polyfill such as https://cdnjs.com/libraries/core-js (which includes much more than is needed) or a minimal definition which resolves the references
https://jsbin.com/sawoqik/edit?html,js,output
A full definition is only needed for GeoTIFF sources, which cannot work in IE as the workers need ES6 support - and ES6 includes Reflect.
It is possible that by connecting the npm package to your project, you can achieve builds that work in IE11. But it is not possible to perform the assembly in the form of a library.
The last build (npm run build-legacy) from the source code that works for me is version 6.4.3.