Leaflet `marker-` assets not included in build.

[erictheise]

I'm chasing down some 404 errors as I work with the new unpkg distribution.

Is there a reason that the Gruntfile explicitly grabs only the layers images?

src: ['layers.png','layers-2x.png'],

[Malvoz]

The reasoning is that Leaflet markers aren't used anymore, see #334. Preferably they shouldn't be fetched in that case...

[erictheise]

leaflet.css still tries to fetch marker-icon.png though.

/* Default icon URLs */
.leaflet-default-icon-path {
	background-image: url(images/marker-icon.png);
	}

Leaving that one, actually all three, in the build seems a smaller price to pay than patching leaflet.css and leaflet-src.js. What do you think?

[Malvoz]

Well, there are issues with using Leaflet as is. For example:

• We're inheriting quite a few accessibility issues. And I don't expect them (for reasons) to be accepting PRs to fix them any time soon.
• I'd like to lower the specificity of selectors in leaflet.css (and mapml.css) in general (it'd give this component a "native feel" to it, but also allow authors to write styles without !important statements).

But forking Leaflet hasn't been discussed much. Maybe it's time to, @prushforth?

I'm okay with adding back the markers in the grunt file for now though.

[prushforth]

Yeah, let's put those back in for now.