Steps to reproduce
Steps to reproduce the behavior:

• open examples page https://leafletjs.com/examples/wms/wms.html

Expected behavior
demos display wms layers on the map

Current behavior
demos does not display wms layers on the map

Environment

• Leaflet version: 1.5
• Browser (with version): chrome 78, firefox 70
• OS/Platform (with version): manjaro

**Additiona

Bug

For the component Marker, the type of value retrieved from onPress={e => console.log(e.nativeEvent)} does not match the documentation NOR the index.d.ts

What is being logged :
{ action: "marker-press", coordinate: { latitude: 0, longitude: 0 }, id: "unknown", target: 77 }

Environment info

React native info output:

For example the client side reprojection examples should link to each other. Same goes for 'Layer Min/Max Resolution' and 'Layer Zoom Limits', which basically achieve the same effect but no one knows this from viewing either one.

Describe the bug 🐛

• Setting the zoom level to floating point numbers doesn't work, the onChange is simply fired again parsing the float into an int.
• eg: setting zoom level to 11.2 will trigger an onChange with 11

To Reproduce 🔍

Steps to reproduce the behavior:

1. set zoom level to 11.2
2. notice how the onChange is fired, overriding the 11.2 with 11

**Expected behav

Instructions: replace text surrounded by '*' with your case, please delete this line.

How to reproduce?

Explain how we can get this issue, if you created a repo with the issue, please add the link, blank if you are submitting a suggestion or improvement

Extra notes

Explain what you expect, feedback, images or anything you consider necessary

I am using

Came across an incorrectly formatted header in the Jazzy docs today:

Looks like there's a missing \n in the inline comments, which should be simple enough to fix.

iOS versions: 4.9.0 (and likely all others since "Related Examples" were added)

maptalks's version and what browser you use?
v0.43.0, chrome

Issue description
Layers do not share WebGL context, which creates glitches when a map has more than one 3d layer. For example a buildings layer with a 3D line will not hide the line behind the buildings.
In particular, I am implementing a 3D terrain layer but this layer will not hide (behind mountains) any other 3d element

@mar-v-in
To do it you have to create a repository called .github, example: https://github.com/micro5k/.github
See: https://github.com/micro5k/.github/blob/master/docs/funding.yml

Then all repositories in the organizations will have the support button, you can see how it appears here: https://github.com/micro5k/microg-unofficial-installer

We should remove glyphicons in favor of font-awesome. Currently we use both.

WIP in the branch: port-doc-sphinx-breathe

Instructions and dependencies here.

• Inspiration:

  • michaeljones/breathe#343
  • https://github.com/michaeljones/breathe
  • https://github.com/fmtlib/fmt

• Motivation:

  • Sphi

From maputnik/editor#563 (comment)

The Light position and Style Renderer tooltips are not fully visible and when scrolled down, the scroll position is set back to the initial position. This issue exists also for some tooltips of the Data Sources modal.

From maputnik/editor#563 (comment)

If you collapse the JSON

I report this issue : QwantResearch/qwantmaps#23

It seems that there is no shoemaker or locksmith on openmaptiles : https://github.com/openmaptiles/openmaptiles/blob/master/layers/poi/mapping.yaml#L117

Could openmaptiles include the shop=locksmith tags ?

Thanks !

The Document here gives ways to optimize the map.

Can level of details too be helpful for smooth rendering?
If we increase the LOD to something more than what we have right now, it will have to render small area compared to the previous LOD. Can that be done?

Problem
It is very difficult to understand how the web documentation is organized, what documentation exists, and how to navigate the documentation. There is no table of contents, and the only way to discover what documentation actually exists is to (1) click continuously on the "next topic" to go through all pages in order, (2) "search" and hope you get lucky, (3) use the "index" that provid

https://jupyter-gmaps.readthedocs.io/en/latest/export.html

Currently I only see 1 solution to export map to HTML file, it requires 2 steps to open it on 8080 port, which is not intuitive for beginners. I would like to see if it's possible to make it as easy as open HTML file by a simple click action.