Hey Rob,
Thank you! I have fixed this
> Btw, this line caught my attention
>
https://github.com/prtksxna/leafleft-map-component/blob/master/leaflet-map-component.html#L10
> You're hard coding a path to `bower_components` but you don't have a
> guarantee that the user will have a `bower_components` dir. Using a
> `.bowerrc` file, the user may have renamed their `bower_components` dir (we
> often rename ours to just "components"). Depending on how leaflet works, you
> may need to take their stylesheet, modify it so it's Shadow DOM friendly,
> and load your own version into your elements.
I had documented this concern in the first issue -
http://git.io/K_klXg - and have fixed it now.
Fixed.
I get really confused with difference between a property and an
attribute. I don't want to call it something else as I am reflecting
it on the DOM. So if you zoom the map by double clicking on it then
the attribute changes too. Is there some documentation that I should
refer to to understand this better?
Fixed.
I have added this to the comment and linked to the mailing list.
Changing the innerHTML of the `leaflet-marker` element whether through
the inspector or through JavaScript does not call the `contentChanged`
-
http://git.io/2Bruog - function and thus doesn't update the popup.
>> I would be grateful if someone could answer these questions. Do you
>> think its worth it to package it and put it on bower and web component
>> registries?
> sure!
Done! I put it up on Bower and a few other places :)
>> Should I add the rest of the Leaflet features and add
>> elements for <leaflet-polygon>, <leaflet-path> etc?
> sure!
Hmm. I am unsure of how I want to expose the interface for these.
These elements will be slightly more complicated. Maybe I should
discuss that on the leaflet mailing list.
> Take a look at the seed-element. It has some sample tests.
The seed-element and the article related to it were very helpful. I
haven't added tests yet but was able to add documentation and deploy
to gh-pages using that documentation
—prtksxna