Jon Koops
Jon Koops
Another reason why we might want to drop support for Internet Explorer is that our tooling is no longer working in newer versions (see https://github.com/Leaflet/Leaflet/pull/8204#issuecomment-1114878906). Some dependencies are already held...
The final results from the [Twitter poll](https://twitter.com/LeafletJS/status/1518606186521804800) are in, I think we have enough information to make an educated decision. I am personally in favor for dropping it for the...
So in essence we'd just use the 'v2' version as a way to drop support for older browsers without actually adding any new features. I think that is perfectly valid,...
Sounds good to me :+1:
I think we're all in agreement here that we want to drop support for all versions of Internet Explorer so I am marking this proposal as accepted.
Closing this as we just branched off for v2, so we can consider this resolved.
I'm not against this adding this as an option. But perhaps this can also easily be done with existing JS features or a small lib?
Just be aware that Lodash is not [tree-shakable](https://developer.mozilla.org/en-US/docs/Glossary/Tree_shaking). So if you are bundling it you are very likely to end up with all of the code in Lodash rather than...
We do not want to add dependencies when we can avoid this. So if this were to be implemented, then it would have to be in Leaflet itself. However I...
I think we should seriously re-consider shipping anything in core that can be accomplished with existing platform APIs or a small library. As our mantra is: > Leaflet is designed...