You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenTopoMap tiles do not have the CORS headers, as the other common tile provider have, than the resulting canvas will be tainted, and then not exportable.
We should:
provide an error to the user for this kind of issue
Investigate on the tileproviders we support to identify which of them have the same problem
- Fixgeosolutions-it#1267. Now if the canvas is tainted, a warning suggest the user how to have a better result
- Removed glitch when leaflet try to save snapshot (a box was appearing in top-right corner)
- Simplified the snapshot creation procedure (triggers)
- Error management in case of tainted canvas in the save mode (see geosolutions-it#1269)
- Various Fixes with wrong sizes of snapshot
- Now leaflet snapshot support resized map when the drawer menu do not overlap
- Increased test coverage
- Fix#1267. Now if the canvas is tainted, a warning suggest the user how to have a better result
- Removed glitch when leaflet try to save snapshot (a box was appearing in top-right corner)
- Simplified the snapshot creation procedure (triggers)
- Error management in case of tainted canvas in the save mode (see #1269)
- Various Fixes with wrong sizes of snapshot
- Now leaflet snapshot support resized map when the drawer menu do not overlap
- Increased test coverage
The OpenTopoMap tiles do not have the CORS headers, as the other common tile provider have, than the resulting canvas will be tainted, and then not exportable.
We should:
The text was updated successfully, but these errors were encountered: