Jon Koops

@mathe42 Nice that you are working on this, but perhaps it's a separate issue from this one as the class syntax is unrelated to improving support for TypeScript users. Perhaps...

I think this might be a useful feature that we could consider for 2.0 so I added it to the milestone. This does not mean this is automatically accepted.

> One positive aspect of including TypeScript compiler in the tool chain is that it allows you to target ES5 while at the same time being able to use most...

Indeed, I have high hopes for type annotations becoming standardized. This would make it a lot easier to build libraries with support for Flow/TypeScript, without the need to have a...

I personally think we should use the button element here, a link is semantically wrong as we aren't actually linking anywhere. This would be a breaking change we can make...

Perfect, we can see if we can land that in another PR. I personally have no objections for adding a `tabindex="0"` here.

In my opinion we can drop support for all versions of Internet Explorer in version 2. Right now the focus for Leaflet is to decrease our giant backlog of issues...

Support for Internet Explorer 11 [will be dropped](https://docs.microsoft.com/en-us/lifecycle/products/internet-explorer-11) on June 15th 2022. I suggest we drop support for Internet Explorer entirely in v2, which should be released after that date....

My main problem with IE11 is it's [crippled support](https://kangax.github.io/compat-table/es6/#ie11) for anything modern JavaScript. Going forward I think our lowest possible compile target should be ES2015.

If anything dropping support will incentivize people to stop supporting it all together. > "Be the change you wish to see in the world." – not Mahatma Gandhi