maps

• [✔️] I've looked at the documentation to make sure the behavior is documented and expected
• [✔️] I'm sure this is a Leaflet code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
• [✔️] I've searched through the issues to make sure it's not yet reported

Steps to reproduce
Steps to reproduce

MGLTilePyramidOfflineRegion should have a countOfTiles method that returns the number of tiles included in the tile pyramid. The implementation would rely on the mbgl::util::tileCount() function added in #9906.

This is the iOS/macOS equivalent to #11108 for Android. It would serve as a built-in alternative to mapbox/turf-swift#47 for applications already using the map SDK, including applica

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

Reproduces on iOS:

• Do some edits
• Enable "Always ask for Internet" dialogue (may be not necessary)
• Open OSM profile. Internet access dialogue appears.
• Allow access for today. The number of edits does not change.
• After re-opening the profile the edits number is updated.

I think it'd be great to be able to move a Task between Projects, likely from the Task's Edit page.

This can help with keeping things organized, as you may not realize you'll need/want new Projects immediately, and it will save you having to either to export/import, or re-upload data (if you've not processed it).

For instance, I'd now like to move my Pix4D example datasets out from the Githu

'react-autocomplete' (https://github.com/reactjs/react-autocomplete) is no longer maintained and causing warnings

react-dom.development.js:12357 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.
• R