Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Leaflet.GridLayer.GoogleMutant
Leaflet.GridLayer.GoogleMutant
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 3
    • Merge Requests 3
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Iván Sánchez Ortega
  • Leaflet.GridLayer.GoogleMutantLeaflet.GridLayer.GoogleMutant
  • Issues
  • #27

Closed
Open
Opened Feb 14, 2017 by Robert Harm@robertharmContributor

broken tiles after panning (+500px) & zooming (4+ levels at once)

update 25.2.2017: generic jsfiddle to reproduce this issue: https://jsfiddle.net/no56t0fh/2/

We encountered a strange behaviour when implementing Google Mutant for our upcoming release. Have a look at the fullscreen map at https://dev.mapsmarker.com/pro/maps/fullscreen/layer/561/ - default map is OpenStreetmap which works without issues:

openstreetmap

Anyway if you switch to a Google Mutant layer afterwards, the tiles are not fully displayed:

google-mutant

To fix this, you have to pan the map several times for all tiles to be loaded correctly.

We couldnt find out yet what exactly is causing this behaviour & would appreciate any help in fixing this issue, which we believe is a general GoogleMutant issue.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: IvanSanchez/Leaflet.GridLayer.GoogleMutant#27