Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] Google map zoom is laggy when dashlane extension is enabled

Aperta
  • Qualcosa non va?
#818 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
react, typescript
Ambito
frontend, web-dev

Direzione di ricerca

Inizia riproducendo il ritardo dello zoom segnalato nell’implementazione di react-google-maps con Dashlane abilitato e disabilitato, usando circa un centinaio di marker. Confronta l’output della console e le modifiche al DOM mostrati nell’issue con la libreria Google Maps standard; il lavoro è completo quando viene identificata una causa lato libreria o una correzione riproducibile e applicabile, ma non sono indicati né un file sorgente né un test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Description

This is very strange. I was porting our google map from the standard google map sdk over to this library. However, I noticed with this implementation that the zoom was laggy. I was able to track down that dashlane was doing some weird stuff via following the console.log events to those dom nodes. I don't have a slimmed down demo for this yet, I'll have to spend some time at night to get that started. I imagine this will be hard to reproduce. Once I disabled dashlane the zoom lag went away

I noticed these logs in the console in the react implementation that weren't there before.

Image Clicking on the element listed, I see dashlane has inserted it's information on the element. Image

Once I uninstall dashlane the issue goes away. However the issue didn't happen at all with the standard google maps libary.

Thank you all for the awesome library! Conflicts between extensions and libraries can be a pain to diagnose.

Steps to Reproduce
  1. Have dashlane installed.
  2. Render maybe a hundred markers.
  3. Zoom in and out. - it should be jittery/laggy
  4. Disable dashlane
  5. try it again and it should be smooth.
Environment
  • Library version: 1.5.2
  • Google maps version: weekly
  • Browser and Version: 139.0.7258.128 (Official Build) (64-bit)
  • OS: Windows 11 23H2
Logs
Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.871 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.871 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.871 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.871 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.871 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.871 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.872 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.872 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.875 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.876 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.876 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.925 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.926 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.926 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.926 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.927 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.927 kwift.CHROME.js:1 Rendering was performed in a subtree hidden by content-visibility. <div style=​"content-visibility:​ hidden;​">​…​</div>​
12:36:28.928
Lingua principale
TypeScript
Stelle
1.9k
Fork
195
Merge medio
2g 11h
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di visgl/react-google-maps

Tutte le issue di visgl/react-google-maps

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.