“ ) siht dnuorakrow ot deen uoy omed nwo ruoy ni neve ,pam eht ot tniop rohcna eht si tniop mottob eht erehw rekram elyts "nip" eht evah ylno nac uoy siht tuohtiWhttps://storage.googleapis.com/gmp-maps-demos/advanced-markers/index.html#weather-marker ) by using `transform: translate(-1.8em,-1.8em)` - but that breaks nice features like the collision behaviour. Ideally it's fully dynamic, but even allowing a choice between the current behaviour & one where it's centred would be enough for all our use cases. ”
“ ot detaler eb dluoc siht thguoht I ,ecnalg tsrif tAhttps://bugs.chromium.org/p/chromium/issues/detail?id=521364 , basically, after appying CSS transform, the computed pixel position is not snapped to the pixel grid, so I tried to extract the pixel values from the CSS transform and round them, but they don't work as expected. So this does seems to be a rendering issue with the text. And then I found an interesting solution, that is to adjust the display of the marker element to 'table', which somehow forces rounding the sub-pixels of the text, see the jsfiddle here: https://jsfiddle.net/6tqzbnx9/5/. ”
“ :ereh elddifsj eht ees ,txet eht fo slexip-bus eht gnidnuor secrof wohemos hcihw ,'elbat' ot tnemele rekram eht fo yalpsid eht tsujda ot si taht ,noitulos gnitseretni na dnuof I neht dnA .txet eht htiw eussi gniredner a eb ot smees seod siht oS .detcepxe sa krow t'nod yeht tub ,meht dnuor dna mrofsnart SSC eht morf seulav lexip eht tcartxe ot deirt I os ,dirg lexip eht ot deppans ton si noitisop lexip detupmoc eht ,mrofsnart SSC gniyppa retfa ,yllacisab ,463125=di?liated/seussi/muimorhc/p/gro.muimorhc.sgub//:sptth ot detaler eb dluoc siht thguoht I ,ecnalg tsrif tAhttps://jsfiddle.net/6tqzbnx9/5/ . ”
“ ) .oot ti htiw eussi gnivah ma I ?devloser eb eussi rulb eht lliw nehwhttps://lottiehome.vercel.app/search ) ”
“
.gniredner eht dexif ,taht gnilbasiDhttps://developer.mozilla.org/en-US/docs/Web/CSS/will-change suggests avoiding it. ”